Automated hazard handling routine activation

ABSTRACT

Disclosed herein are example embodiments for automated hazard handling routine activation. For certain example embodiments, at least one machine, such as an unoccupied flying vehicle (UFV), may: (i) detect at least one motivation to activate at least one automated hazard handling routine of the UFV; or (ii) activate at least one automated hazard handling routine of the UFV based at least partially on at least one motivation. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, or so forth.

If an Application Data Sheet (ADS) has been filed on the filing date ofthis application, it is incorporated by reference herein. Anyapplications claimed on the ADS for priority under 35 U.S.C. §§119, 120,121, or 365(c), and any and all parent, grandparent, great-grandparent,etc. applications of such applications, are also incorporated byreference, including any priority claims made in those applications andany material incorporated by reference, to the extent such subjectmatter is not inconsistent herewith.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is related to and/or claims the benefit of theearliest available effective filing date(s) from the following listedapplication(s) (the “Priority Applications”), if any, listed below(e.g., claims earliest available priority dates for other thanprovisional patent applications or claims benefits under 35 USC §119(e)for provisional patent applications, for any and all parent,grandparent, great-grandparent, etc. applications of the PriorityApplication(s)). In addition, the present application is related to the“Related Applications,” if any, listed below.

PRIORITY APPLICATIONS

-   -   (1) For purposes of the USPTO extra-statutory requirements, the        present application constitutes a continuation-in-part of U.S.        patent application Ser. No. 13/720,694, entitled “Inter-Vehicle        Communication for Hazard Handling for an Unoccupied Flying        Vehicle (UFV)”, naming Royce A. Levien, Richard T. Lord,        Robert W. Lord, Mark A. Malamud, John D. Rinaldo, Jr., and        Lowell L. Wood, Jr. as inventors, filed 19 Dec. 2012 (with Atty.        Docket No. SE1-0783-US), which is currently co-pending or is an        application of which a currently co-pending application is        entitled to the benefit of the filing date.    -   (2) For purposes of the USPTO extra-statutory requirements, the        present application constitutes a continuation-in-part of U.S.        patent application Ser. No. 13/722,874, entitled “Unoccupied        Flying Vehicle (UFV) Inter-Vehicle Communication for Hazard        Handling”, naming Royce A. Levien, Richard T. Lord, Robert W.        Lord, Mark A. Malamud, John D. Rinaldo, Jr., and Lowell L. Wood,        Jr. as inventors, filed 20 Dec. 2012 (with Atty. Docket No.        SE1-0784-US), which is currently co-pending or is an application        of which a currently co-pending application is entitled to the        benefit of the filing date.    -   (3) For purposes of the USPTO extra-statutory requirements, the        present application constitutes a continuation-in-part of U.S.        patent application Ser. No. 13/728,642, entitled “Inter-Vehicle        Flight Attribute Communication for an Unoccupied Flying Vehicle        (UFV)”, naming Royce A. Levien, Richard T. Lord, Robert W. Lord,        Mark A. Malamud, John D. Rinaldo, Jr., and Lowell L. Wood, Jr.        as inventors, filed 27 Dec. 2012 (with Atty. Docket No.        SE1-0785-US), which is currently co-pending or is an application        of which a currently co-pending application is entitled to the        benefit of the filing date.    -   (4) For purposes of the USPTO extra-statutory requirements, the        present application constitutes a continuation-in-part of U.S.        patent application Ser. No. 13/730,202, entitled “Base Station        Control for an Unoccupied Flying Vehicle (UFV)”, naming Royce A.        Levien, Richard T. Lord, Robert W. Lord, Mark A. Malamud,        John D. Rinaldo, Jr., and Lowell L. Wood, Jr. as inventors,        filed 28 Dec. 2012 (with Atty. Docket No. SE1-0786-US), which is        currently co-pending or is an application of which a currently        co-pending application is entitled to the benefit of the filing        date.    -   (5) For purposes of the USPTO extra-statutory requirements, the        present application constitutes a continuation-in-part of U.S.        patent application Ser. No. 13/731,363, entitled “Automated        Hazard Handling Routine Engagement”, naming Royce A. Levien,        Richard T. Lord, Robert W. Lord, Mark A. Malamud, John D.        Rinaldo, Jr., and Lowell L. Wood, Jr. as inventors, filed 31        Dec. 2012 (on same date herewith) (with Atty. Docket No.        SE1-0787-US), which is currently co-pending or is an application        of which a currently co-pending application is entitled to the        benefit of the filing date.    -   (6) For purposes of the USPTO extra-statutory requirements, the        present application constitutes a continuation-in-part of U.S.        patent application Ser. No. 13/______, entitled “Collision        Targeting for an Unoccupied Flying Vehicle (UFV)”, naming        Royce A. Levien, Richard T. Lord, Robert W. Lord, Mark A.        Malamud, John D. Rinaldo, Jr., and Lowell L. Wood, Jr. as        inventors, filed 31 Dec. 2012 (on same date herewith) (with        Atty. Docket No. SE1-0789-US), which is currently co-pending or        is an application of which a currently co-pending application is        entitled to the benefit of the filing date.    -   (7) For purposes of the USPTO extra-statutory requirements, the        present application constitutes a continuation-in-part of U.S.        patent application Ser. No. 13/______, entitled “Collision        Targeting for Hazard Handling”, naming Royce A. Levien,        Richard T. Lord, Robert W. Lord, Mark A. Malamud, John D.        Rinaldo, Jr., and Lowell L. Wood, Jr. as inventors, filed 31        Dec. 2012 (on same date herewith) (with Atty. Docket No.        SE1-0790-US), which is currently co-pending or is an application        of which a currently co-pending application is entitled to the        benefit of the filing date.

RELATED APPLICATIONS

None

The United States Patent Office (USPTO) has published a notice to theeffect that the USPTO's computer programs require that patent applicantsreference both a serial number and indicate whether an application is acontinuation, continuation-in-part, or divisional of a parentapplication. Stephen G. Kunin, Benefit of Prior-Filed Application, USPTOOfficial Gazette Mar. 18, 2003. The USPTO further has provided forms forthe Application Data Sheet which allow automatic loading ofbibliographic data but which require identification of each applicationas a continuation, continuation-in-part, or divisional of a parentapplication. The present Applicant Entity (hereinafter “Applicant”) hasprovided above a specific reference to the application(s) from whichpriority is being claimed as recited by statute. Applicant understandsthat the statute is unambiguous in its specific reference language anddoes not require either a serial number or any characterization, such as“continuation” or “continuation-in-part,” for claiming priority to U.S.patent applications. Notwithstanding the foregoing, Applicantunderstands that the USPTO's computer programs have certain data entryrequirements, and hence Applicant has provided designation(s) of arelationship between the present application and its parentapplication(s) as set forth above and in any ADS filed in thisapplication, but expressly points out that such designation(s) are notto be construed in any way as any type of commentary and/or admission asto whether or not the present application contains any new matter inaddition to the matter of its parent application(s).

If the listings of applications provided above are inconsistent with thelistings provided via an ADS, it is the intent of the Applicant to claimpriority to each application that appears in the Priority Applicationssection of the ADS and to each application that appears in the PriorityApplications section of this application.

All subject matter of the Priority Applications and the RelatedApplications and of any and all parent, grandparent, great-grandparent,etc. applications of the Priority Applications and the RelatedApplications, including any priority claims, is incorporated herein byreference to the extent such subject matter is not inconsistentherewith.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 is a schematic diagram of at least one unoccupied flying vehicle(UFV) in accordance with certain example embodiments.

FIG. 2 is a schematic diagram of example realizations for at least oneUFV in accordance with certain example embodiments.

FIGS. 3A-3C are schematic diagrams of example UFV hazard handlingscenarios or environments in accordance with certain exampleembodiments.

FIG. 4 is a schematic diagram of an example unoccupied flying vehicle(UFV) including one or more example components in accordance withcertain example embodiments.

FIG. 5 is a schematic diagram of an example base station, which may bein communication with at least one UFV, including one or more examplecomponents for a base station in accordance with certain exampleembodiments.

FIG. 6A is a schematic diagram of an example UFV that has one or morefunctional modules or one or more operational components in accordancewith certain example embodiments.

FIG. 6B is a schematic diagram of an example base station that has oneor more functional modules or one or more operational components inaccordance with certain example embodiments.

FIG. 7A is a schematic diagram that includes at least one examplemachine, such as an unoccupied flying vehicle (UFV), that is capable ofhandling scenarios for automated hazard handling routine activation inaccordance with certain example embodiments.

FIGS. 7B-7E are schematic diagrams that include at least one examplemachine and that depict example scenarios for implementing automatedhazard handling routine activation in accordance with certain exampleembodiments.

FIG. 8A is a flow diagram illustrating an example method for at leastone machine with regard to automated hazard handling routine activationin accordance with certain example embodiments.

FIGS. 8B-8E depict example additions or alternatives for a flow diagramof FIG. 8A in accordance with certain example embodiments.

FIGS. 9A-9B depict example additions or alternatives for a flow diagramof FIG. 8A in accordance with certain example embodiments.

FIG. 10A depicts example additions or alternatives for a flow diagram ofFIG. 8A in accordance with certain example embodiments.

DETAILED DESCRIPTION

In the following detailed description, reference is made to theaccompanying drawings, which form a part hereof. In the drawings,similar symbols typically identify similar components, unless contextdictates otherwise. The illustrative embodiments described in thedetailed description, drawings, and claims are not meant to be limiting.Other embodiments may be utilized, and other changes may be made,without departing from the spirit or scope of the subject matterpresented here.

FIG. 1 is a schematic diagram 100 of at least one unoccupied flyingvehicle (UFV) in accordance with certain example embodiments. As shownin FIG. 1, by way of example but not limitation, schematic diagram 100may include at least one unoccupied flying vehicle (UFV) 102 or at leastone remote UFV 102R. For certain example implementations, any particularUFV: may be, comprise, or include a UFV 102, such as a local UFV, or maybe, comprise, or include a remote UFV 102R. A given UFV scenario may beconsidered, analyzed, operated, viewed, or a combination thereof, etc.from a perspective of at least one local UFV 102 with regard to one ormore remote UFVs 102R. Disclosure herein or in the accompany drawings,which form a part hereof, that is directed to a UFV 102 may additionallyor alternatively be applicable to a remote UFV 102R, unless contextdictates otherwise. However, claimed subject matter is not limited toany particular described embodiments, implementations, examples, etc.

For certain example embodiments, a UFV 102 may comprise or include avehicle that is not capable of being occupied by a human pilot (e.g.,due to size, shape, power, atmospheric pressure, or a combinationthereof, etc. constraints), a vehicle that is not designed to seat orotherwise safely support a person, a vehicle that is not controllable byan onboard human pilot, a vehicle that is being autonomously controlledat least partially by at least one onboard module, a vehicle that isbeing autonomously controlled at least partially by at least oneoff-board module, a combination thereof, or so forth. For certainexample embodiments, a UFV 102 may be at least comparable to or maycomprise or include at least a portion of any one or more of: anunmanned aerial vehicle (UAV), a remotely piloted vehicle (RPV), anunmanned combat air vehicle (UCAV), an unmanned aircraft (UA), a drone,an optionally-piloted vehicle (OPV) that is not currently beingcontrolled by an on-board pilot, a remotely piloted aircraft (RPA), aremotely operated aircraft (ROA), a radio-controlled aircraft (R/Caircraft), an unmanned-aircraft vehicle system (UAVS), an unmannedaircraft system (UAS), a small unmanned air system (sUAS), a combinationthereof, or so forth. For certain example embodiments, a UFV 102 may flythrough a fluid (e.g., the earth's atmosphere or the air), through atleast a partial vacuum (e.g., space or near-earth orbit), a combinationthereof, or so forth. However, claimed subject matter is not limited toany particular described embodiments, implementations, examples, etc.

FIG. 2 is a schematic diagram 200 of example realizations for at leastone UFV in accordance with certain example embodiments. As shown in FIG.2, by way of example but not limitation, schematic diagram 200 mayinclude at least one unoccupied flying vehicle (UFV) 102, at least onefixed wing UFV 102 a, at least one rotary wing UFV 102 b, at least oneornithopter UFV 102 c, at least one lighter-than-air (LTA) UFV 102 d, atleast one tilt-wing UFV 102 e, at least one hybrid UFV 102 f, or atleast one other type of UFV 102 g. However, claimed subject matter isnot limited to any particular described embodiments, implementations,examples, etc.

For certain example embodiments, a UFV 102 may be realized as describedby any one or more of the examples in this paragraph. First, a UFV 102may be realized as a fixed wing UFV 102 a, such as a propeller-drivenbiplane or a jet plane. Second, a UFV 102 may be realized as a rotarywing UFV 102 b, such as a helicopter or a gyrodyne. Third, a UFV 102 maybe realized as an ornithopter UFV 102 c, such as small craft that hasflapping wings like an animal (e.g., like a dragonfly, bee, bird, orbat, etc.). Fourth, a UFV 102 may be realized as an LTA UFV 102 d, suchas a blimp, a balloon, or a dirigible. Fifth, a UFV 102 may be realizedas a tilt-wing UFV 102 e, such as a propeller-driven airplane with wingsthat rotate at least during vertical takeoff or landing. Sixth, a UFV102 may be realized as a hybrid UFV 102 f that combines one or morecapabilities or structural characteristics of at least one fixed wingUFV 102 a, at least one rotary wing UFV 102 b, at least one ornithopterUFV 102 c, at least one LTA UFV 102 d, at least one tilt-wing UFV 102 e,or at least one other UFV 102 g. Seventh, a UFV 102 may be realized asan other type of UFV 102 g, such as a tilt-rotor craft, a submarine, arocket, a spaceship, a satellite, a vertical take-off and landing (VTOL)craft, a combination thereof, or so forth. However, claimed subjectmatter is not limited to any particular described embodiments,implementations, examples, etc.

For certain example embodiments, a UFV 102 may additionally oralternatively be realized so as to have one or more features,capabilities, structural characteristics, or a combination thereof, etc.as described by any one or more of the examples in this paragraph.First, a UFV 102 may include one rotor, two rotors (e.g., in a tandem,transverse, coaxial, or intermeshing, etc. configuration), three rotors,four rotors (e.g., a quadcopter, or a quadrotor, etc.), a combinationthereof, or so forth. Second, a UFV 102 may include a propeller engine,a jet engine, an electric engine, a rocket engine, a ramjet or scramjetengine, a combination thereof, or so forth. Third, a UFV 102 may have atleast one wing (e.g., a monoplane, a biplane, or a triplane, etc. in astacked or tandem wing configuration), which may include a straightwing, a swept wing, a delta wing, a variable sweep wing, a combinationthereof, or so forth. Fourth, a UFV 102 may be realized as having afuselage, as having a flying wing structure, as having a blended-wingbody, a combination thereof, or so forth. However, claimed subjectmatter is not limited to any particular described embodiments,implementations, examples, etc.

FIGS. 3A-3C are schematic diagrams 300A-300C, respectively, of exampleUFV hazard handling scenarios or environments in accordance with certainexample embodiments. As shown in FIGS. 3A-3C, by way of example but notlimitation, each of schematic diagrams 300A-300C may include at leastone unoccupied flying vehicle (UFV) 102, at least one remote UFV 102R,or ground 304. In each scenario or environment of schematic diagrams300A-300C, at least one UFV 102 may be flying above ground 304 andendeavoring to detect, sense, avoid, manage, mitigate, communicateabout, coordinate over, eliminate, predict, remove, account for, remedyaftermath caused by, cooperate to address, or a combination thereof,etc. at least one hazard. For certain example embodiments, hazards mayinclude, but are not limited to, other unoccupied flying vehicles,occupied flying vehicles, ground 304, buildings or other structures (notshown) on ground 304, moving objects, weather conditions, stationaryobjects, some combination thereof, or so forth. A UFV 102 may beattempting to accomplish a mission, an objective, a task, a combinationthereof, or so forth. In operation, a UFV may be in communication withat least one remote UFV, at least one pilot-occupied flying vehicle(POFV), at least one base station (not shown in FIG. 3A), at least oneother entity, a combination thereof, or so forth. Although scenarios orenvironments of schematic diagrams 300A-300C may be shown in thedrawings or described herein individually or separately, at leastportions or aspects of such scenarios or environments may be implementedor may otherwise occur at least partially jointly, simultaneously intime, overlapping in space, as part of a single or extended operationaltheater, a combination thereof, or so forth. However, claimed subjectmatter is not limited to any particular described embodiments,implementations, examples, etc.

FIG. 3A is a schematic diagram 300A of an example UFV hazard handlingscenario or environment in accordance with certain example embodiments.As shown in FIG. 3A, by way of example but not limitation, schematicdiagram 300A may include at least one UFV 102, at least one remote UFV102R, at least one pilot-occupied flying vehicle (POFV) 302, or ground304. More specifically, schematic diagram 300A may include a POFV 302, afirst POFV 302(1), or a second POFV 302(2). For certain exampleembodiments, a POFV 302 may comprise or include a vehicle that iscurrently being controlled by an onboard human pilot. For certainexample embodiments, ground 304 may include or comprise at least aportion of the earth, a landscape, a cityscape, a prairie, a hill, amountain, a combination thereof, or so forth. However, claimed subjectmatter is not limited to any particular described embodiments,implementations, examples, etc.

FIG. 3B is a schematic diagram 300B of another example UFV hazardhandling scenario or environment in accordance with certain exampleembodiments. As shown in FIG. 3B, by way of example but not limitation,schematic diagram 300B may include at least one UFV 102, at least oneremote UFV 102R, ground 304, or at least one base station 306. Morespecifically, schematic diagram 300B may include a remote UFV 102R, afirst remote UFV 102R(1), or a second remote UFV 102R(2). For certainexample embodiments, a base station 306 may comprise or include amachine that is adapted to at least partially control or is capable ofcontrolling a UFV 102 from a distance via at least one wirelesscommunication (not explicitly shown in FIG. 3B). For certain exampleimplementations, a base station 306 may be fixed within a building or ona mobile ground vehicle, may be capable of being hand-held, may beincorporated into or as part of another flying vehicle, a combinationthereof, or so forth. For certain example implementations, a basestation 306 may include or comprise a handheld controller (e.g., as maybe used with an R/C model plane) for actual or near line-of-sightcontrol, a workstation-sized or brief-case-sized controller that ismobile for operation out in the field (e.g., for police or corporatepurposes), a larger apparatus that is typically stationary or may behoused in a secret or private building miles from an operational theater(e.g., for military or governmental purposes), a server-sized ordistributed apparatus that provides control for a swarm of UFVs (e.g.,for careful monitoring of a construction, agricultural, or warehousesite), some combination thereof, or so forth. For certain exampleembodiments, a base station 306 may be controlling at least one UFV,such as first remote UFV 102R(1) or second remote UFV 102R(2), while notcontrolling at least one other UFV, such as UFV 102 or remote UFV 102R(although it may be monitoring a UFV without controlling it). However,claimed subject matter is not limited to any particular describedembodiments, implementations, examples, etc.

FIG. 3C is a schematic diagram 300C of another example UFV hazardhandling scenario or environment in accordance with certain exampleembodiments. As shown in FIG. 3C, by way of example but not limitation,schematic diagram 300C may include at least one UFV 102, at least oneremote UFV 102R, at least one POFV 302, ground 304, at least one basestation 306, at least one communication 308, or at least one flight path312. More specifically, UFV 102 may include at least one UFV hazardhandling module 310, or communication 308 may include at least onetransmission 308T or at least one reception 308R. For certain exampleembodiments, a UFV 102 may transmit at least one transmission 308T to orreceive at least one reception 308R from at least one of a remote UFV102R, a POFV 302, a base station 306, a combination thereof, or soforth. For certain example embodiments, a UFV hazard handling module 310may affect or at least partially control a flight path of a UFV 102 atleast partially based on at least one of a transmission 308T or areception 308R. For certain example embodiments, a flight path 312 maycomprise or include any one or more of: a flight trajectory, a heading,a speed, a direction, a velocity, an acceleration, a position, analtitude, a stability level, a destination, a two-dimensional course ora three-dimensional course through air or space, a course through aspherical geometrical space, a time or times at which a course is to betraversed, a time or times at which one or more positions or one or morealtitudes are to be attained, a time or times at which other flightcharacteristic(s) are to be attained, extrapolated position-time stamppairs based on current flight characteristic(s), extrapolatedaltitude-time stamp pairs based on current flight characteristic(s), acombination thereof, or so forth. However, claimed subject matter is notlimited to any particular described embodiments, implementations,examples, etc.

For certain example embodiments, a remote UFV 102R, a POFV 302, or abase station 306 may participate in at least one communication 308, suchas a transmission 308T or a reception 308R, with at least one UFV 102.Although not explicitly shown in schematic diagram 300C, for certainexample embodiments, each of remote UFV 102R, POFV 302, or base station306 may additionally or alternatively exchange at least onecommunication 308 with at least one other of remote UFV 102R, POFV 302,or base station 306. For certain example implementations, a remote UFV102R may transmit at least one transmission 308T to or receive at leastone reception 308R from at least one of a UFV 102, another remote UFV102R, a POFV 302, a base station 306, a combination thereof, or soforth. For certain example implementations, a POFV 302 may transmit atleast one transmission 308T to or receive at least one reception 308Rfrom at least one of a UFV 102, a remote UFV 102R, another POFV 302, abase station 306, a combination thereof, or so forth. For certainexample implementations, a base station 306 may transmit at least onetransmission 308T to or receive at least one reception 308R from atleast one of a UFV 102, a remote UFV 102R, a POFV 302, another basestation 306, a combination thereof, or so forth. However, claimedsubject matter is not limited to any particular described embodiments,implementations, examples, etc.

FIG. 4 is a schematic diagram 400 of an example unoccupied flyingvehicle (UFV) including one or more example components in accordancewith certain example embodiments. As shown in FIG. 4, a UFV 102 mayinclude one or more components such as: at least one processor 402, oneor more media 404, logic 406, circuitry 408, at least one communicationinterface 410, at least one interconnect 412, at least one power source414, at least one motility mechanism 416, one or more sensors 418, somecombination thereof, or so forth. Furthermore, as shown in schematicdiagram 400, one or more media 404 may include one or more instructions420, at least one hazard handling 422 routine, one or more flightattributes 424, some combination thereof, or so forth; a communicationinterface 410 may include at least one wireless communication interface410 a, at least one wired communication interface 410 b, somecombination thereof, or so forth; or a motility mechanism 416 mayinclude at least one power train 416 a, at least one steering assembly416 b, some combination thereof, or so forth. However, a UFV 102 mayalternatively include more, fewer, or different component(s) from thosethat are illustrated without departing from claimed subject matter.

For certain example embodiments, a UFV 102 may include or comprise atleast one machine that is capable of flight, flight control processing,(local) flight control, some combination thereof, or so forth. UFV 102may include, for example, a computing platform or any electronic devicehaving at least one processor or memory. Processor 402 may include, byway of example but not limitation, any one or more of a general-purposeprocessor, a specific-purpose processor, a digital signal processor(DSP), a processing unit, some combination thereof, or so forth. Aprocessing unit may be implemented, for example, with one or moreapplication specific integrated circuits (ASICs), DSPs, digital signalprocessing devices (DSPDs), programmable logic devices (PLDs), fieldprogrammable gate arrays (FPGAs), processors generally, processingcores, discrete/fixed logic circuitry, controllers, micro-controllers,microprocessors, some combination thereof, or so forth. Media 404 maybear, store, contain, include, provide access to, or a combinationthereof, etc. instructions 420, which may be executable by a processor402; at least one hazard handling 422 routine, which may at leastpartially form at least a portion of instructions 420; one or moreflight attributes 424; some combination thereof; or so forth.Instructions 420 may include or comprise, by way of example but notlimitation, a program, a module, an application or app (e.g., that isnative, that runs in a browser, that runs within a virtual machine, or acombination thereof, etc.), an operating system, or a combinationthereof, etc. or portion thereof; operational data structures; sourcecode, object code, just-in-time (JIT) compiled code, or a combinationthereof, etc.; processor-executable instructions; other code; somecombination thereof; or so forth. Media 404 may include, by way ofexample but not limitation, processor-accessible or non-transitory media(e.g., memory, random access memory (RAM), read only memory (ROM), flashmemory, hard drives, disk-based media, disc-based media, magneticstorage, optical storage, volatile memory, nonvolatile memory, or acombination thereof, etc.) that is capable of bearing instructions, oneor more hazard handling routines, one or more flight attributes, somecombination thereof, or so forth.

For certain example embodiments, execution of instructions 420 by one ormore processors 402 may transform at least a portion of UFV 102 into aspecial-purpose computing device, apparatus, platform, some combinationthereof, or so forth. Instructions 420 may include, for example,instructions that are capable of realizing at least a portion of one ormore flow diagrams, methods, processes, procedures, operations,functionality, technology, mechanisms, or a combination thereof, etc.that are described herein or illustrated in the accompanying drawings. Ahazard handling 422 routine may include, for example, instructions thatare capable of realizing at least a portion of one or more flowdiagrams, methods, processes, procedures, operations, functionality,technology, mechanisms, or a combination thereof, etc. that aredescribed herein or illustrated in the accompanying drawings or that aredirected toward detecting, sensing, avoiding, managing, mitigating,communicating about, coordinating over, eliminating, predicting,removing, accounting for, remedying aftermath caused by, cooperating toaddress, or a combination thereof, etc. at least one hazard. A flightattribute 424 may include, for example, data describing or representingat least one flight attribute of a UFV, such as one or more flightcharacteristics, one or more flight capabilities, a combination thereof,or so forth. Additionally or alternatively, at least a portion of flightattributes 424 may be at least partially accessible to or integratedwith hazard handling 422.

For certain example embodiments, logic 406 may include hardware,software, firmware, discrete/fixed logic circuitry, or a combinationthereof, etc. that is capable of performing or facilitating performanceof flow diagrams, methods, processes, procedures, operations,functionality, technology, mechanisms, or a combination thereof, etc.that are described herein or illustrated in the accompanying drawings.Circuitry 408 may include hardware, software, firmware, discrete/fixedlogic circuitry, or a combination thereof, etc. that is capable ofperforming or facilitating performance of flow diagrams, methods,processes, procedures, operations, functionality, technology,mechanisms, or a combination thereof, etc. that are described herein orillustrated in the accompanying drawings, wherein circuitry 408 includesat least one physical or hardware component or aspect.

For certain example embodiments, one or more communication interfaces410 may provide one or more interfaces between UFV 102 and anothermachine or a person/operator. With respect to a person/operator, acommunication interface 410 may include, by way of example but notlimitation, a screen, a speaker, keys/buttons, a microphone, or otherperson-device input/output apparatuses. A wireless communicationinterface 410 a or a wired communication interface 410 b may also oralternatively include, by way of example but not limitation, atransceiver (e.g., a transmitter or a receiver), a radio, an antenna, awired interface connector or other similar apparatus (e.g., a networkconnector, a universal serial bus (USB) connector, a proprietaryconnector, a Thunderbolt® or Light Peak® connector, or a combinationthereof, etc.), a physical or logical network adapter or port, afrequency converter, a baseband processor, a photoreceptor, or acombination thereof, etc. to communicate wireless signals or wiredsignals via one or more wireless communication links or wiredcommunication links, respectively. Communications with at least onecommunication interface 410 may enable transmitting, receiving, orinitiating of transmissions, just to name a few examples.

For certain example embodiments, at least one interconnect 412 mayenable signal communication between or among components of UFV 102.Interconnect 412 may include, by way of example but not limitation, oneor more buses, channels, switching fabrics, some combination thereof, orso forth. Although not explicitly illustrated in FIG. 4, one or morecomponents of UFV 102 may be coupled to interconnect 412 via a discreteor integrated interface. By way of example only, one or more interfacesmay couple a communication interface 410 or a processor 402 to at leastone interconnect 412. For certain example embodiments, at least onepower source 414 may provide power to one or more components of UFV 102.Power source 414 may include, by way of example but not limitation, abattery, a power connector, a solar power source or charger, amechanical power source or charger, a fuel source, a generator, anengine, some combination thereof, or so forth.

For certain example embodiments, at least one sensor 418 may sense,produce, or otherwise provide at least one sensor value. Sensors 418 mayinclude, by way of example only, a camera, a microphone, anaccelerometer, a thermometer, a satellite positioning system (SPS)sensor, a barometer, a humidity sensor, a compass, an altimeter, anairspeed detector, a gyroscope, a magnetometer, a pressure sensor, anoscillation detector, a light sensor, an inertial measurement unit(IMU), a tactile sensor, a touch sensor, a flexibility sensor, amicroelectromechanical system (MEMS), some combination thereof, or soforth. Values provided by at least one sensor 418 may include, by way ofexample but not limitation, an image/video, a sound recording, anacceleration value, a temperature, one or more SPS coordinates, abarometric pressure, a humidity level, a compass direction, an altitude,an airspeed, a gyroscopic value, a magnetic reading, a pressure value,an oscillation value, an ambient light reading, inertial readings, touchdetections, proximate object location, flex detections, some combinationthereof, or so forth.

For certain example embodiments, a motility mechanism 416 may enable UFV102 to fly, overcome gravitational forces, overcome wind resistance ordrag, accelerate, avoid a hazard, some combination thereof, or so forth.For certain example embodiments, a power train 416 a of a motilitymechanism 416 may include one or more components that work separately orat least partially together to transform or convert stored energy intokinetic energy in order to propel UFV 102. For certain exampleimplementations, a power train 416 a may include at least one engine, atleast one transmission, one or more blades or propellers, at least onemotor, some combination thereof, or so forth. For certain exampleembodiments, a steering assembly 416 b of a motility mechanism 416 mayinclude one or more components that work separately or at leastpartially together to transform propulsive kinetic energy into forward,backward, up, down, right, left, a combination thereof, etc. movement orsome other directionality change for a UFV. For certain exampleimplementations, a steering assembly 416 b may include at least oneaileron, at least one rudder, at least one elevator, one or more bladesor propellers, at least one transmission that routes power to differentmotors or other propulsive components, at least one rotor disk tilter,at least one blade pitch angle changer, or a combination thereof, or soforth. Although illustrated separately in schematic diagram 400, powertrain 416 a and steering assembly 416 b may be implemented at leastpartially jointly to realize motility mechanism 416.

However, claimed subject matter is not limited to any particulardescribed embodiments, implementations, examples, or so forth. Forinstance, it should be understood that for certain exampleimplementations components that are illustrated separately in FIG. 4 maynot necessarily be separate or mutually exclusive. For example, a givencomponent may provide multiple functionalities. By way of example only,a single component such as a photodetector may function as a wirelesscommunication interface 410 a or a sensor 418. Additionally oralternatively, one or more instructions 420 may function to realize orembody at least part of hazard handling 422 or flight attributes 424.

It should also be understood that for certain example implementationscomponents that are illustrated in schematic diagram 400 or describedherein may or may not be integral with or integrated into or onto a UFV102. For example, a component may be removably connected to a UFV 102, acomponent may be wirelessly coupled to a UFV 102, some combinationthereof, or so forth. By way of example only, instructions 420 may bestored on a removable card having at least one medium 404. Additionallyor alternatively, at least a portion of a motility mechanism 416, suchas an engine or a fuel source, may be detachable from or replaceablewith a UFV 102. However, claimed subject matter is not limited to anyparticular described embodiments, implementations, examples, etc.

FIG. 5 is a schematic diagram 500 of an example base station, which maybe in communication with at least one UFV (not shown in FIG. 5),including one or more example components for a base station inaccordance with certain example embodiments. As shown in FIG. 5, a basestation 306 may include one or more components such as: at least oneprocessor 502, one or more media 504, logic 506, circuitry 508, at leastone communication interface 510, at least one interconnect 512, at leastone power source 514, at least one entity interface 516, somecombination thereof, or so forth. Furthermore, as shown in schematicdiagram 500, one or more media 504 may include one or more instructions518, at least one hazard handling 520 routine, at least one flightattribute 522, some combination thereof, or so forth; or communicationinterface 510 may include at least one wireless communication interface510 a, at least one wired communication interface 510 b, somecombination thereof, or so forth. However, a base station 306 mayalternatively include more, fewer, or different component(s) from thosethat are illustrated without departing from claimed subject matter.

For certain example embodiments, a base station 306 may include orcomprise at least one machine that is capable of flight controlprocessing, (distant) flight control, some combination thereof, or soforth. Base station 306 may include, for example, a computing platformor any electronic device or devices having at least one processor ormemory. Processor 502 may include, by way of example but not limitation,any one or more of a general-purpose processor, a specific-purposeprocessor, a digital signal processor (DSP), a processing unit, somecombination thereof, or so forth. A processing unit may be implemented,for example, with one or more application specific integrated circuits(ASICs), DSPs, digital signal processing devices (DSPDs), programmablelogic devices (PLDs), field programmable gate arrays (FPGAs), processorsgenerally, processing cores, discrete/fixed logic circuitry,controllers, micro-controllers, microprocessors, some combinationthereof, or so forth. Media 504 may bear, store, contain, include,provide access to, or a combination thereof, etc. instructions 518,which may be executable by a processor 502; at least one hazard handling520 routine, which may at least partially form at least a portion ofinstructions 518; one or more flight attributes 522; some combinationthereof; or so forth. Instructions 518 may include or comprise, by wayof example but not limitation, a program, a module, an application orapp (e.g., that is native, that runs in a browser, that runs within avirtual machine or server, or a combination thereof, etc.), an operatingsystem, or a combination thereof, etc. or portion thereof; operationaldata structures; source code, object code, just-in-time (JIT) compiledcode, or a combination thereof, etc.; processor-executable instructions;other code; some combination thereof; or so forth. Media 504 mayinclude, by way of example but not limitation, processor-accessible ornon-transitory media (e.g., memory, random access memory (RAM), readonly memory (ROM), flash memory, hard drives, disk-based media,disc-based media, magnetic storage, optical storage, volatile memory,nonvolatile memory, or a combination thereof, etc.) that is capable ofbearing instructions, one or more hazard handling routines, one or moreflight attributes, some combination thereof, or so forth.

For certain example embodiments, execution of instructions 518 by one ormore processors 502 may transform at least a portion of base station 306into a special-purpose computing device, apparatus, platform, somecombination thereof, or so forth. Instructions 518 may include, forexample, instructions that are capable of realizing at least a portionof one or more flow diagrams methods, processes, procedures, operations,functionality, technology, mechanisms, or a combination thereof, etc.that are described herein or illustrated in the accompanying drawings. Ahazard handling 520 routine may include, for example, instructions thatare capable of realizing at least a portion of one or more flowdiagrams, methods, processes, procedures, operations, functionality,technology, mechanisms, or a combination thereof, etc. that aredescribed herein or illustrated in the accompanying drawings and thatare directed toward interacting with at least one UFV to facilitatedetecting, seeing, avoiding, managing, mitigating, communicating about,coordinating over, eliminating, predicting, removing, accounting for,remedying aftermath caused by, cooperating to address, or a combinationthereof, etc. at least one hazard. A flight attribute 522 may include,for example, data describing or representing at least one flightattribute, such as one or more flight characteristics, one or moreflight capabilities, a combination thereof, etc. of at least one UFVthat base station 306 is communicating with, is at least partiallycontrolling, is monitoring, some combination thereof, or so forth.Additionally or alternatively, at least a portion of flight attributes522 may be at least partially accessible to or integrated with hazardhandling 520.

For certain example embodiments, logic 506 may include hardware,software, firmware, discrete/fixed logic circuitry, or a combinationthereof, etc. that is capable of performing or facilitating performanceof flow diagrams, methods, processes, procedures, operations,functionality, technology, mechanisms, or a combination thereof, etc.that are described herein or illustrated in the accompanying drawings.Circuitry 508 may include hardware, software, firmware, discrete/fixedlogic circuitry, or a combination thereof, etc. that is capable ofperforming or facilitating performance of flow diagrams, methods,processes, procedures, operations, functionality, technology,mechanisms, or a combination thereof, etc. that are described herein orillustrated in the accompanying drawings, wherein circuitry 508 includesat least one physical or hardware component or aspect.

For certain example embodiments, one or more communication interfaces510 may provide one or more interfaces between base station 306 andanother machine or a person/operator/entity directly or indirectly. Awireless communication interface 510 a or a wired communicationinterface 510 b may also or alternatively include, by way of example butnot limitation, a transceiver (e.g., a transmitter or a receiver), aradio, an antenna, a wired interface connector or other similarapparatus (e.g., a network connector, a universal serial bus (USB)connector, a proprietary connector, a Thunderbolt® or Light Peak®connector, a gateway, or a combination thereof, etc.), a physical orlogical network adapter or port, a frequency converter, a basebandprocessor, an internet or telecommunications backbone connector, a fiberoptic connector, a storage area network (SAN) connector, or acombination thereof, etc. to communicate wireless signals or wiredsignals via one or more wireless communication links or wiredcommunication links, respectively. Communications with at least onecommunication interface 510 may enable transmitting, receiving, orinitiating of transmissions, just to name a few examples.

For certain example embodiments, at least one interconnect 512 mayenable signal communication between or among components of base station306. Interconnect 512 may include, by way of example but not limitation,one or more buses, channels, switching fabrics, local area networks(LANs), storage area networks (SANs), some combination thereof, or soforth. Although not explicitly illustrated in FIG. 5, one or morecomponents of base station 306 may be coupled to interconnect 512 via adiscrete or integrated interface. By way of example only, one or moreinterfaces may couple a processor 502 or a medium 504 to at least oneinterconnect 512. For certain example embodiments, at least one powersource 514 may provide power to one or more components of base station306. Power source 514 may include, by way of example but not limitation,a power connector for accessing an electrical grid, a fuel cell, a solarpower source, one or more batteries, some combination thereof, or soforth.

For certain example embodiments, an entity interface 516 may enable oneor more entities (e.g., a person, a group, an electronic agent, arobotic entity, or a combination thereof, etc.) to provide input to orreceive output from base station 306. Interactions between an entity anda base station may relate, by way of example but not limitation, toinputting or outputting instructions, commands, settings, flightcharacteristics, flight capabilities, some combination thereof, or soforth. Certain entity interfaces 516 may enable both entity input andentity output at base station 306 or over at least one network link.

However, claimed subject matter is not limited to any particulardescribed embodiments, implementations, examples, or so forth. Forinstance, it should be understood that for certain exampleimplementations components that are illustrated separately in FIG. 5need not necessarily be separate or mutually exclusive. For example, agiven component may provide multiple functionalities. By way of exampleonly, hard-wired logic 506 may form circuitry 508. Additionally oralternatively, a single component such as a connector may function as acommunication interface 510 or as an entity interface 516. Additionallyor alternatively, one or more instructions 518 may function to realizeor embody at least part of hazard handling 520 or flight attributes 522.

It should also be understood that for certain example implementationscomponents that are illustrated in schematic diagram 500 or describedherein may not be integral or integrated with a base station 306. Forexample, a component may be removably connected to a base station 306, acomponent may be wirelessly coupled to a base station 306, one or morecomponents of a base station 306 may be geographically distributed orseparated from one another, some combination thereof, or so forth. Byway of example only, instructions 518 may be stored on one medium 504,and flight attributes 522 (or another portion of instructions 518) maybe stored on a different medium 504, which may be part or a same serveror a part of a different server of, e.g., a server farm. Additionally oralternatively, respective processor-media pairs, if any, may bephysically realized on different or respective server blades or servercontainers for a base station 306 that is implemented on serverhardware. However, claimed subject matter is not limited to anyparticular described embodiments, implementations, examples, etc.

FIG. 6A is a schematic diagram 600A of an example UFV that has one ormore functional modules or one or more operational components inaccordance with certain example embodiments. As shown in FIG. 6A,example UFV 102 of schematic diagram 600A may include, by way of examplebut not limitation, at least one UFV hazard handling module 310, atleast one communication interface 410, at least one interconnect 412, atleast one motility mechanism 416, one or more sensors 418, or at leastone UFV flight control module 602. More specifically, communicationinterface 410 may include at least one radio 604, or so forth; ormotility mechanism 416 may include at least one power train 416 a, atleast one steering assembly 416 b, some combination thereof, or soforth. However, a UFV 102 may alternatively include more, fewer, ordifferent module(s) or component(s) from those that are illustratedwithout departing from claimed subject matter.

For certain example embodiments, a UFV hazard handling module 310 or aUFV flight control module 602 may operate to implement, perform,facilitate performance of, or a combination thereof, etc. one or moreflow diagrams, methods, processes, procedures, operations,functionality, technology, modules, mechanisms, or a combinationthereof, etc. that are described herein or illustrated in theaccompanying drawings or that relate to handling an actual or apotential hazard. Example aspects related to hazard handling in a UFVcontext are described further herein above and below. Although UFVhazard handling module 310 and UFV flight control module 602 areillustrated separately in schematic diagram 600A, they may additionallyor alternatively be implemented at least partially in combination,jointly, with an overlapping functionality, some combination thereof, orso forth. For certain example embodiments, and by way of example but notlimitation, at least a portion of one or more modules (e.g., module 702,module 704, or a combination thereof, etc.) that are described hereinbelow with particular reference to FIG. 7A may be implemented as atleast part of UFV hazard handling module 310, as at least part of UFVflight control module 602, some combination thereof, or so forth.However, claimed subject matter is not limited to any particulardescribed embodiments, implementations, examples, etc.

For certain example embodiments, a module of a UFV 102 may include or becomprised of at least one processor (e.g., a processor 402 of FIG. 4,etc.), one or more media (e.g., a medium 404 of FIG. 4, etc.),executable instructions (e.g., processor-executable instructions,instructions 420 of FIG. 4, computer-implementable instructions, etc.)incorporated into one or more media, logic (e.g., logic 406 of FIG. 4,etc.), circuitry (e.g., circuitry 408 of FIG. 4, etc.), other describedor illustrated component(s), may be comprised as otherwise describedherein, some combination thereof, or so forth. For certain exampleimplementations, one or more modules (e.g., a UFV hazard handling module310, a UFV flight control module 602, or a combination thereof, etc.) ofat least one UFV 102 may function or interoperate with one or moremodules of at least one remote UFV 102R, at least one POFV 302, at leastone base station 306 (e.g., each of FIGS. 3A-3C or FIG. 6B), or acombination thereof, etc. via at least one radio 604 of UFV 102.However, claimed subject matter is not limited to any particulardescribed embodiments, implementations, examples, etc.

For certain example embodiments, UFV 102 may be in constant, infrequent,regular, irregular, intermittent, occasional, scheduled, unscheduled, acombination thereof, etc. communication with at least one remote UFV102R, at least one POFV 302, at least one base station 306, or acombination thereof, etc. via at least one radio 604. One or moresensors 418 or at least one radio 604 may feed sensor readings,telemetry, flight attributes, weather conditions, topographical maps,coordination parameters, one or more automated hazard handling routines,a combination thereof, etc. to UFV hazard handling module 310, UFVflight control module 602, a combination thereof, or so forth. Forcertain example implementations, UFV hazard handling module 310 may atleast make hazard-related flight control decisions or provide flightcontrol input to UFV flight control module 602 with regard to handlingactual or potential hazards. For certain example implementations, UFVflight control module 602 may at least partially make flight controldecisions or provide flight control commands to motility mechanism 416so as to implement flight control decisions, including, by way ofexample but not limitation, based at least partly on flight controlinput provided by UFV hazard handling module 310. Additionally oralternatively, a UFV hazard handling module 310 may supply flightcontrol input, including by way of example but not limitation with atleast one flight control command, directly (e.g., without routing itfirst through UFV flight control module 602) to motility mechanism 416.To implement flight control decisions, including flight controlcommands, motility mechanism 416 may employ power train 416 a to provideat least one propulsive force or may employ steering assembly 416 b toprovide at least one directional change. However, claimed subject matteris not limited to any particular described embodiments, implementations,examples, etc.

FIG. 6B is a schematic diagram 600B of an example base station that hasone or more functional modules or one or more operational components inaccordance with certain example embodiments. As shown in FIG. 6B,example base station 306 of schematic diagram 600B may include, by wayof example but not limitation, at least one communication interface 510,at least one interconnect 512, at least one UFV flight control module652, at least one sensor 656, at least one UFV flight coordinationmodule 658, or at least one UFV hazard handling module 660. Morespecifically, communication interface 510 may include at least one radio654, or so forth. However, a base station 306 may alternatively includemore, fewer, or different module(s) or component(s) from those that areillustrated without departing from claimed subject matter. Moreover,module(s) or component(s) that are illustrated in schematic diagram 600Bmay alternatively or additionally be separate from or non-integratedwith a base station 306, such as being external to a housing of orremotely-accessible to a base station 306, for certain exampleimplementations.

For certain example embodiments, a UFV hazard handling module 660, a UFVflight coordination module 658, or a UFV flight control module 652 mayoperate to implement, perform, facilitate performance of, or acombination thereof, etc. one or more flow diagrams, methods, processes,procedures, operations, functionality, technology, modules, mechanisms,or a combination thereof, etc. that are described herein or illustratedin the accompanying drawings or that relate to handling of an actual ora potential hazard. Example aspects related to hazard handling in a UFVcontext with at least one base station are described further hereinabove and below. Although UFV hazard handling module 660, UFV flightcontrol module 652, and UFV flight coordination module 658 areillustrated separately in schematic diagram 600B, they may additionallyor alternatively be implemented at least partially in combination,jointly, with an overlapping functionality, some combination thereof, orso forth. However, claimed subject matter is not limited to anyparticular described embodiments, implementations, examples, etc.

For certain example embodiments, a module of a base station 306 mayinclude or be comprised of at least one processor (e.g., a processor 502of FIG. 5, etc.), one or more media (e.g., a medium 504 of FIG. 5,etc.), executable instructions (e.g., processor-executable instructions,instructions 518 of FIG. 5, computer-implementable instructions, etc.)incorporated into one or more media, logic (e.g., logic 506 of FIG. 5,etc.), circuitry (e.g., circuitry 508 of FIG. 5, etc.), other describedor illustrated component(s), may be comprised as otherwise describedherein, some combination thereof, or so forth. For certain exampleembodiments, one or more modules (e.g., a UFV hazard handling module660, a UFV flight control module 652, a UFV flight coordination module658, or a combination thereof, etc.) of at least one base station 306may function or interoperate with one or more modules of at least oneUFV 102, at least one remote UFV 102R, at least one POFV 302, at leastone other base station 306 (e.g., each of FIG. 3A-3C or 6A), or acombination thereof, etc. via at least one radio 654 (or via a wiredconnection (not explicitly shown in FIG. 6B) of a communicationinterface 510) of base station 306. However, claimed subject matter isnot limited to any particular described embodiments, implementations,examples, etc.

For certain example embodiments, a base station 306 may be in constant,infrequent, regular, irregular, intermittent, occasional, scheduled,unscheduled, a combination thereof, etc. communication with at least oneUFV 102, at least one remote UFV 102R, at least one POFV 302, at leastone first UFV, at least one second UFV, at least one other base station306, or a combination thereof, etc. via at least one radio 654. Forcertain example implementations, one or more sensors 656 (e.g., such asone or more of example sensor types described herein above withparticular reference to sensor 418 (e.g., for a UFV 102 of FIG. 4)) orat least one radio 654 may feed sensor readings, telemetry, flightattributes, weather conditions, topographical maps, coordinationparameters, at least one automated hazard handling routine, acombination thereof, etc. to UFV hazard handling module 660, UFV flightcontrol module 652, UFV flight coordination module 658, a combinationthereof, or so forth. For certain example embodiments, UFV hazardhandling module 660 may at least make hazard-related flight controldecisions or provide flight control input to UFV flight control module652 or UFV flight coordination module 658 with regard to handling actualor potential hazards. For certain example embodiments, UFV flightcoordination module 658 may at least make multi-UFV coordination flightcontrol decisions or provide flight control input to UFV flight controlmodule 652 or UFV hazard handling module 660 with regard to coordinatingtwo or more UFVs, with or without involvement by another base station.For certain example embodiments, UFV flight control module 652 may atleast partially make flight control decisions or formulate flightcontrol commands (e.g., for transmission via radio 654 to a UFV 102 andpossible application to a motility mechanism 416 (e.g., of FIG. 6A)thereof) so as to realize flight control decisions, including, by way ofexample but not limitation, based at least partly on flight controlinput provided by at least UFV hazard handling module 660 or UFV flightcoordination module 658. However, claimed subject matter is not limitedto any particular described embodiments, implementations, examples, etc.

FIG. 7A is a schematic diagram 700A that includes at least one examplemachine, such as an unoccupied flying vehicle (UFV), that is capable ofhandling scenarios for automated hazard handling routine activation inaccordance with certain example embodiments. As shown in FIG. 7A, by wayof example but not limitation, schematic diagram 700A includes at leastone machine that may include an activation motivation detection module702 or an automated hazard handling routine activation module 704. Morespecifically, schematic diagram 700A may include a machine that includesor comprises at least one UFV 102. By way of example but not limitation,an activation motivation detection module 702 or an automated hazardhandling routine activation module 704 may include or comprise or berealized with at least one processor that executes instructions (e.g.,sequentially, in parallel, at least partially overlapping in atime-multiplexed fashion, at least partially across multiple cores, or acombination thereof, etc.) as at least one special-purpose computingcomponent, or otherwise as described herein. However, claimed subjectmatter is not limited to any particular described embodiments,implementations, examples, etc.

For certain example embodiments, an activation motivation detectionmodule 702 or an automated hazard handling routine activation module 704may be implemented separately or at least partially jointly or incombination. For certain example implementations, an activationmotivation detection module 702 may be configured to detect at least onemotivation to activate at least one automated hazard handling routine ofthe UFV. For certain example implementations, an automated hazardhandling routine activation module 704 may be configured to activate atleast one automated hazard handling routine of a UFV based at leastpartially on at least one motivation. However, claimed subject matter isnot limited to any particular described embodiments, implementations,examples, etc.

FIGS. 7B-7E are schematic diagrams 700B-700E that include at least oneexample machine and that depict example scenarios for implementingautomated hazard handling routine activation in accordance with certainexample embodiments. As shown in FIGS. 7B-7E, by way of example but notlimitation, one or more of schematic diagrams 700B-700E may include atleast one UFV 102, at least one motivation 708, at least one automatedhazard handling routine 710, at least one detection 712, or at least oneactivation 714. Each of schematic diagrams 700B-700E may includealternative or additional depictions, which may relate to automatedhazard handling routine activation, as described herein. In addition toor in alternative to description herein below with specific reference toFIGS. 7B-7E, illustrated aspects of schematic diagrams 700B-700E may berelevant to example description with reference to FIG. 8A-8E, 9A-9B, or10A. However, claimed subject matter is not limited to any particulardescribed embodiments, implementations, examples, etc.

As shown in FIG. 7B, by way of example but not limitation, schematicdiagram 700B may include at least one UFV 102, at least one motivation708, at least one automated hazard handling routine 710, at least onedetection 712, or at least one activation 714. For certain exampleembodiments, at least one activation motivation detection module 702(e.g., of FIG. 7A) of a UFV 102 may effectuate at least one detection712 of at least one motivation 708 to activate at least one automatedhazard handling routine 710. For certain example implementations, atleast one motivation 708 may include or comprise at least one reason, atleast one stimulus, at least one impetus, at least one justification, atleast one incentive, at least one trigger, at least one inducement, somecombination thereof, or so forth. For certain example embodiments, atleast one automated hazard handling routine activation module 704 (e.g.,of FIG. 7A) of a UFV 102 may effectuate at least one activation 714 ofat least one automated hazard handling routine 710 based at leastpartially on at least one motivation 708 that is detected. For certainexample implementations, at least one automated hazard handling routine710 may include or comprise at least one automatic approach to avoidinga hazard, at least one programmed response to a potential hazard, atleast one electronic control for flight, at least one default procedurefor ameliorating or mitigating a hazardous situation, at least oneautomated mechanism for reducing a likelihood of becoming a hazard, somecombination thereof, or so forth. However, claimed subject matter is notlimited to any particular described embodiments, implementations,examples, etc. Additional or alternative description that may berelevant to schematic diagram 700B is provided herein below withparticular reference to one or more of any of FIGS. 8A-8E, FIGS. 9A-9B,or FIG. 10A.

As shown in FIG. 7C, by way of example but not limitation, schematicdiagram 700C may include at least one UFV 102, at least one motivation708, at least one automated hazard handling routine 710, at least onedetection 712, or at least one activation 714, at least one remote UFV102R, proximity zone 718, at least one comparison 720, at least oneposition 722, at least one position 722R, at least one satellitepositioning system (SPS) coordinate 724, at least one SPS coordinate724R, at least one proximity alert 726, at least one base station 306,air traffic coordination unit 728, at least one physical contact 730, atleast one object 732, at least one accelerometer 734, at least onecontact sensor 736, at least one time 738, at least one identification740, at least one comparison 742, at least one functionality loss 744,at least one component 746, at least one visual spectrum sensor 748, orat least one SPS unit 750. However, claimed subject matter is notlimited to any particular described embodiments, implementations,examples, etc. Additional or alternative description that may berelevant to schematic diagram 700C is provided herein below withparticular reference to one or more of any of FIGS. 8A-8E, FIGS. 9A-9B,or FIG. 10A.

As shown in FIG. 7D, by way of example but not limitation, schematicdiagram 700D may include at least one UFV 102, at least one motivation708, at least one automated hazard handling routine 710, at least onedetection 712, or at least one activation 714, at least one map 754, atleast one flight path 756, at least one three-dimensional representation758, at least one controlled descent 760, at least one broadcast 762, atleast one maneuverability quality 764, at least one plan 766, at leastone governmental constraint 768, at least one populated area 770, or atleast one heat signature 772. However, claimed subject matter is notlimited to any particular described embodiments, implementations,examples, etc. Additional or alternative description that may berelevant to schematic diagram 700D is provided herein below withparticular reference to one or more of any of FIGS. 8A-8E, FIGS. 9A-9B,or FIG. 10A.

As shown in FIG. 7E, by way of example but not limitation, schematicdiagram 700E may include at least one UFV 102, at least one remote UFV102R, at least one base station 306, at least one motivation 708, atleast one automated hazard handling routine 710, at least one detection712, or at least one activation 714, at least one received communication776, at least one sensor 778, at least one deactivation 780, at leastone deactivation command 782, at least one authentication 784, at leastone verification 786, or at least one deactivation code 788. However,claimed subject matter is not limited to any particular describedembodiments, implementations, examples, etc. Additional or alternativedescription that may be relevant to schematic diagram 700E is providedherein below with particular reference to one or more of any of FIGS.8A-8E, FIGS. 9A-9B, or FIG. 10A.

Following are a series of flowcharts depicting implementations. For easeof understanding, the flowcharts are organized such that the initialflowcharts present implementations via an example implementation andthereafter the following flowcharts present alternate implementationsand/or expansions of the initial flowchart(s) as either sub-componentoperations or additional component operations building on one or moreearlier-presented flowcharts. Those having skill in the art willappreciate that the style of presentation utilized herein (e.g.,beginning with a presentation of a flowchart(s) presenting an exampleimplementation and thereafter providing additions to and/or furtherdetails in subsequent flowcharts) generally allows for a rapid and easyunderstanding of the various process implementations. In addition, thoseskilled in the art will further appreciate that the style ofpresentation used herein also lends itself well to modular and/orobject-oriented program design paradigms.

FIG. 8A is a flow diagram 800A illustrating an example method for atleast one machine with regard to automated hazard handling routineactivation in accordance with certain example embodiments. Asillustrated, flow diagram 800A may include any of operations 802-804.Although operations 802-804 are shown or described in a particularorder, it should be understood that methods may be performed inalternative manners without departing from claimed subject matter,including, but not limited to, with a different order or number ofoperations or with a different relationship between or among operations.Also, at least some operation(s) of flow diagram 800A may be performedso as to be fully or partially overlapping with other operation(s). Forcertain example embodiments, one or more operations of flow diagram 800Amay be performed by at least one machine (e.g., a UFV 102 or at least aportion thereof).

For certain example embodiments, a method for hazard handling for anunoccupied flying vehicle (UFV) (e.g., that includes, involves,addresses, reacts to, or a combination thereof, etc. or other otherwisehandles at least one remote UFV 102R, at least one first remote UFV102R(1), at least one second remote UFV 102R(2), at least one POFV 302,at least one other object that may present a collision risk, at leastone weather-related condition, at least one obstacle to a missionobjective, at least one hindrance to accomplishing a task, at least onedelay to achieving a goal, or a combination thereof, etc.), which methodmay be at least partially implemented using hardware (e.g., circuitry,at least one processor, processor-accessible memory, at least onemodule, or a combination thereof, etc.) of a machine such as a UFV, mayinclude an operation 802 or an operation 804. An operation 802 may bedirected at least partially to detecting at least one motivation toactivate at least one automated hazard handling routine of the UFV. Forcertain example implementations, at least one machine may detect (e.g.,ascertain, discover, encounter, identify, spot, determine, or acombination thereof, etc., such as via at least one detection 712) atleast one motivation 708 (e.g., a reason, a stimulus, an impetus, ajustification, an incentive, a trigger, an inducement, or a combinationthereof, etc.) to activate at least one automated hazard handlingroutine 710 (e.g., at least one automatic approach to avoiding a hazard,at least one programmed response to a potential hazard, at least oneelectronic control for flight, at least one default procedure forameliorating or mitigating a hazardous situation, at least one automatedmechanism for reducing a likelihood of becoming a hazard, or acombination thereof, etc. that is realized as at least part of at leastone module, that is encoded into circuitry, that is being performed byat least part of at least one machine, or a combination thereof, etc.)of an unoccupied flying vehicle (UFV) 102 (e.g., a UAV, an RPV, a UCAV,a UA, an RPA, an ROA, an R/C aircraft, a UAVS, a UAS, an sUAS, or acombination thereof, etc.). By way of example but not limitation, atleast one UFV may detect at least one motivation to activate at leastone automated hazard handling routine of the UFV (e.g., a UAV maydiscern an impetus to activate a procedure of the UAV that is intendedto mitigate or dodge a hazard, such as a proximate UAV or an upcomingedifice). However, claimed subject matter is not limited to anyparticular described embodiments, implementations, examples, etc.

For certain example embodiments, an operation 804 may be directed atleast partially to activating the at least one automated hazard handlingroutine of the UFV based at least partially on the at least onemotivation. For certain example implementations, at least one machinemay activate (e.g., set in operation, start, put into force, use, enableinput into flight control, commence, institute, or a combinationthereof, etc., such as via at least one activation 714) at least oneautomated hazard handling routine 710 of a UFV 102 based at leastpartially on at least one motivation 708. By way of example but notlimitation, at least one UFV may activate the at least one automatedhazard handling routine of the UFV based at least partially on the atleast one motivation (e.g., a UAV may start or begin relying on aprocedure that adjusts a flight path of the UAV to avoid approaching aflight trajectory of a proximate UAV or an upcoming side of an edifice).However, claimed subject matter is not limited to any particulardescribed embodiments, implementations, examples, etc.

FIGS. 8B-8E depict example additions or alternatives for a flow diagramof FIG. 8A in accordance with certain example embodiments. Asillustrated, flow diagrams of FIGS. 8B-8E may include any of theillustrated or described operations. Although operations are shown ordescribed in a particular order or with a particular relationship to oneor more other operations, it should be understood that methods may beperformed in alternative manners without departing from claimed subjectmatter, including, but not limited to, with a different order or numberof operations or with a different relationship between or amongoperations (e.g., operations that are illustrated as nested blocks arenot necessarily subsidiary operations and may instead be performedindependently). Also, at least some operation(s) of flow diagrams ofFIGS. 8B-8E may be performed so as to be fully or partially overlappingwith other operation(s). For certain example embodiments, one or moreoperations of flow diagrams 800B-800E (of FIGS. 8B-8E) may be performedby at least one machine (e.g., a UFV 102 or at least a portion thereof).

FIG. 8B illustrates a flow diagram 800B having example operations 810,812, or 814. For certain example embodiments, an operation 810 may bedirected at least partially to wherein the detecting at least onemotivation to activate at least one automated hazard handling routine ofthe UFV (of operation 802) includes detecting at least one other UFVwithin a proximity zone of the UFV. For certain example implementations,at least one machine may detect (e.g., via at least one detection 712)at least one other UFV (e.g., a remote UFV 102R) within a proximity zone718 (e.g., a two-dimensional radius, a three-dimensional radius, abuffer zone, a spatial distance value, a temporal distance value, anindication of a region within which other UFVs are to be considered apotential hazard, an indication of a region within which other UFVs arefactored into flight path decisions, a value that is dependent onrespective UFV headings, a value that is dependent on respective UFVspeeds, or a combination thereof, etc.) of a UFV. By way of example butnot limitation, at least one UFV may detect at least one other UFVwithin a proximity zone of the UFV. (e.g., a UAV may discover thatanother UAV is within a given threshold buffer distance, such as onemile or 50 feet, of the UAV). However, claimed subject matter is notlimited to any particular described embodiments, implementations,examples, etc.

For certain example embodiments, an operation 812 may be directed atleast partially to wherein the detecting at least one other UFV within aproximity zone of the UFV (of operation 810) includes comparing aposition of the UFV with a position of the at least one other UFV. Forcertain example implementations, at least one machine may compare 720(e.g., analyze, determine at least one similarity, determine at leastone difference, find a Euclidean or spherical distance between, or acombination thereof, etc.) a position 722 (e.g., at least one locationabove or on the earth; one or more geographical coordinates; one or moresatellite positioning service (SPS) coordinates, such as GPS, GLONASS,or Galileo coordinates, that are at least partially determined using atleast one satellite; one or more map coordinates; at least one referenceto at least one determinable position, such as a landmark, a waypoint,or an address; one or more cardinal directions indegrees/minutes/seconds; at least one longitude or latitude; or acombination thereof; etc.) of a UFV 102 with a position 722R (e.g., atleast one location above or on the earth; one or more geographicalcoordinates; one or more satellite positioning service (SPS)coordinates, such as GPS, GLONASS, or Galileo coordinates, that are atleast partially determined using at least one satellite; one or more mapcoordinates; at least one reference to at least one determinableposition, such as a landmark, a waypoint, or an address; one or morecardinal directions in degrees/minutes/seconds; at least one longitudeor latitude; or a combination thereof; etc.) of at least one other UFV102R. By way of example but not limitation, at least one UFV may comparea position of the UFV with a position of the at least one other UFV.(e.g., a UAV may compare a first location corresponding to its positionwith a second location corresponding to a position of another UAV todetermine if a distance between the first location and the secondlocation is less than a minimum threshold buffer distance, such as 100feet or 1000 meters). However, claimed subject matter is not limited toany particular described embodiments, implementations, examples, etc.

For certain example embodiments, an operation 814 may be directed atleast partially to wherein the comparing a position of the UFV with aposition of the at least one other UFV (of operation 812) includescomparing one or more satellite positioning system (SPS) coordinatescorresponding to the position of the UFV with one or more SPScoordinates corresponding to the position of the at least one other UFV.For certain example implementations, at least one machine may compare720 one or more satellite positioning system (SPS) coordinates 724(e.g., one or more coordinates that are at least partially determinedusing at least one satellite, GPS coordinates, GLONASS coordinates,Galileo coordinates, or a combination thereof, etc.) corresponding to aposition 722 of a UFV 102 with one or more SPS coordinates 724R (e.g.,one or more coordinates that are at least partially determined using atleast one satellite, GPS coordinates, GLONASS coordinates, Galileocoordinates, or a combination thereof, etc.) corresponding to a position722R of at least one other UFV 102R. By way of example but notlimitation, at least one UFV may compare one or more SPS coordinatescorresponding to the position of the UFV with one or more SPScoordinates corresponding to the position of the at least one other UFV.(e.g., a UAV may use first GPS coordinates of a first locationcorresponding to its position and second GPS coordinates of a secondlocation corresponding to a position of another UAV to determine if adistance between the first and the second GPS coordinates is less than agovernment-instituted threshold buffer distance, such as 20 feet or 500meters). However, claimed subject matter is not limited to anyparticular described embodiments, implementations, examples, etc.

FIG. 8C illustrates a flow diagram 800C having example operations 810(which is described herein above with particular reference to at leastFIG. 8B), 818, 820, 822, or 824. For certain example embodiments, anoperation 818 may be directed at least partially to wherein thedetecting at least one other UFV within a proximity zone of the UFV (ofoperation 810) includes receiving at the UFV at least one proximityalert with respect to the at least one other UFV. For certain exampleimplementations, at least one machine may receive at a UFV 102 at leastone proximity alert 726 (e.g., a transmitted alarm, a wireless signal, amessage, a UFV flight coordination communication, or a combinationthereof, etc. that indicates that at least one UFV is within a proximityzone 718—e.g., a two-dimensional radius, a three-dimensional radius, abuffer zone, a spatial distance value, a temporal distance value, anindication of a region within which other UFVs are to be considered apotential hazard, an indication of a region within which other UFVs arefactored into flight path decisions, a value that is dependent onrespective UFV headings, a value that is dependent on respective UFVspeeds, or a combination thereof, etc.) with respect to at least oneother UFV 102R. By way of example but not limitation, at least one UFVmay receive at the UFV at least one proximity alert with respect to theat least one other UFV. (e.g., a UAV may receive a communication, suchas a message or a signal, indicative that another UAV generically oranother UAV that is specifically identified is within a minimumthreshold buffer of the UAV, which minimum threshold buffer may be basedon spatial distance between two or more vehicles or on temporal distancethat may be impacted by directional headings or relative speeds of twoor more vehicles). However, claimed subject matter is not limited to anyparticular described embodiments, implementations, examples, etc.

For certain example embodiments, an operation 820 may be directed atleast partially to wherein the receiving at the UFV at least oneproximity alert with respect to the at least one other UFV (of operation818) includes receiving at the UFV the at least one proximity alert fromthe at least one other UFV. For certain example implementations, atleast one machine may receive at a UFV 102 at least one proximity alert726 from at least one other UFV 102R. By way of example but notlimitation, at least one UFV may receive at the UFV the at least oneproximity alert from the at least one other UFV. (e.g., a UAV mayreceive a communication from a particular UAV that indicates that theparticular UAV is within a minimum threshold buffer distance from theUAV). However, claimed subject matter is not limited to any particulardescribed embodiments, implementations, examples, etc.

For certain example embodiments, an operation 822 may be directed atleast partially to wherein the receiving at the UFV at least oneproximity alert with respect to the at least one other UFV (of operation818) includes receiving at the UFV the at least one proximity alert froma base station that is associated with the UFV. For certain exampleimplementations, at least one machine may receive at a UFV 102 at leastone proximity alert 726 from a base station 306 that is associated with(e.g., corresponds to, is related to, is linked to, is empowered tocontrol, is capable of adjusting a flight path of, or a combinationthereof, etc.) UFV 102. By way of example but not limitation, at leastone UFV may receive at the UFV the at least one proximity alert from abase station that is associated with the UFV. (e.g., a UAV may receive acommunication from a base station that is capable of sending controllingsignals to the UAV, with the communication indicative that the UAV isless than a first threshold buffer distance from at least one otherUAV—if the UAV continues to get closer, it may receive anothercommunication indicative that the UAV is now less than a second, smallerthreshold buffer distance from the at least one other UAV). However,claimed subject matter is not limited to any particular describedembodiments, implementations, examples, etc.

For certain example embodiments, an operation 824 may be directed atleast partially to wherein the receiving at the UFV at least oneproximity alert with respect to the at least one other UFV (of operation818) includes receiving at the UFV the at least one proximity alert froman air traffic coordination unit. For certain example implementations,at least one machine may receive at a UFV 102 at least one proximityalert 726 from an air traffic coordination unit 728 (e.g., a multi-UFVbase station 306, a tower or antenna and associated circuitry forcoordinating UFVs in the vicinity of the tower or antenna, an apparatusdeployed in the field at least proximate to a region for which theapparatus is responsible for coordinating UFV flight traffic, aprivately-owned apparatus, an apparatus owned by an industry consortium,a government-provided apparatus—such as one placed into service ormonitored by the FAA, an apparatus that is at least partly remote from aregion having UFVs to be coordinated—such as one that is accessible viathe internet or one or more telecommunications networks, or acombination thereof, etc.). By way of example but not limitation, atleast one UFV may receive at the UFV the at least one proximity alertfrom an air traffic coordination unit. (e.g., a UAV may receive acommunication from an air traffic coordination unit that is designed toat least coordinate UAV air traffic across multiple UAVs, including UAVshaving different operators or owners, with the received communicationindicative that the UAV is less than a particular threshold bufferdistance that is applicable to UAVs flying in a particular region thatis associated with the air traffic coordination unit). However, claimedsubject matter is not limited to any particular described embodiments,implementations, examples, etc.

FIG. 8D illustrates a flow diagram 800D having example operations 828,830, 832, 834, or 836. For certain example embodiments, an operation 828may be directed at least partially to wherein the detecting at least onemotivation to activate at least one automated hazard handling routine ofthe UFV (of operation 802) includes detecting physical contact with atleast one object. For certain example implementations, at least onemachine may detect (e.g., via at least one detection 712) physicalcontact 730 (e.g., physical touch, graze, sideswipe, collision, impact,scrape, hit, bump, crash, or a combination thereof, etc.) with at leastone object 732 (e.g., another UFV, a POFV, a building, a fence, a tower,a hill, a billboard, a mountain, a land vehicle such as a car or bus ortruck, a wall, a tree, or a combination thereof, etc.). By way ofexample but not limitation, at least one UFV may detect physical contactwith at least one object. (e.g., a UAV may discern that the UAV hasimpacted, touched, grazed, collided with, or a combination thereof, etc.at least one object, such as another UAV, a building, a person, a car, ahillside, a tower, or a combination thereof, etc.). However, claimedsubject matter is not limited to any particular described embodiments,implementations, examples, etc.

For certain example embodiments, an operation 830 may be directed atleast partially to wherein the detecting physical contact with at leastone object (of operation 828) includes detecting the physical contactwith the at least one object using at least one accelerometer. Forcertain example implementations, at least one machine may detectphysical contact 730 with at least one object 732 using at least oneaccelerometer 734 (e.g., a device that measures acceleration, properacceleration, g-force acceleration, or a combination thereof, etc.; asingle-axis accelerometer; a multi-axis accelerometer; a piezoelectricaccelerometer; a capacitive accelerometer; a micro electro-mechanicalsystems (MEMS) accelerometer; some combination thereof; or so forth). Byway of example but not limitation, at least one UFV may detect thephysical contact with the at least one object using at least oneaccelerometer. (e.g., a UAV may detect that it has impacted a buildingif a negative acceleration value obtained via at least one accelerometerexceeds a specified negative acceleration threshold). However, claimedsubject matter is not limited to any particular described embodiments,implementations, examples, etc.

For certain example embodiments, an operation 832 may be directed atleast partially to wherein the detecting physical contact with at leastone object (of operation 828) includes detecting the physical contactwith the at least one object using at least one contact sensor. Forcertain example implementations, at least one machine may detectphysical contact 730 with at least one object 732 using at least onecontact sensor 736 (e.g., a device that senses mechanical contact andproduces a signal responsive thereto, a tactile sensor, a sensor withhaptic perception, a physical switch sensor, a whisker sensor, or acombination thereof, etc.). By way of example but not limitation, atleast one UFV may detect the physical contact with the at least oneobject using at least one contact sensor. (e.g., a UAV may detect thatit has impacted a tower if a contact switch or whisker mounted on anexterior of the UAV is tripped or triggered). However, claimed subjectmatter is not limited to any particular described embodiments,implementations, examples, etc.

For certain example embodiments, an operation 834 may be directed atleast partially to wherein the detecting physical contact with at leastone object (of operation 828) includes detecting the physical contactwith at least one other UFV. For certain example implementations, atleast one machine may detect physical contact 730 with at least oneother UFV (e.g., with a remote UFV 102R as an object 732). By way ofexample but not limitation, at least one UFV may detect the physicalcontact with at least one other UFV. (e.g., a UAV may detect that it hasat least grazed or bumped another UAV while both UAVs are in flight).However, claimed subject matter is not limited to any particulardescribed embodiments, implementations, examples, etc.

For certain example embodiments, an operation 836 may be directed atleast partially to wherein the detecting the physical contact with atleast one other UFV (of operation 834) includes identifying the at leastone other UFV via at least one comparison including at least one timecorresponding to at least one contact detection by the at least oneother UFV. For certain example implementations, at least one machine mayidentify 740 (e.g., select from between or among two or more options,determine an alphanumeric designation, differentiate from between oramong two or more UFV possibilities, determine at least an approximatelocation of a UFV, or a combination thereof, etc.) at least one other(or remote) UFV 102R (with which physical contact 730 is detected) viaat least one comparison 742 (e.g., analyze, determine at least onesimilarity, determine at least one difference, find a length of timebetween, or a combination thereof, etc.) including at least one time 738corresponding to at least one contact detection by at least one other(or remote) UFV 102R. By way of example but not limitation, at least oneUFV may identify the at least one other UFV via at least one comparisonincluding at least one time corresponding to at least one contactdetection by the at least one other UFV. (e.g., a UAV may identify aparticular UAV that it sideswiped by matching a time noted by anotherUAV that experienced contact, which noted time may be explicitlyincluded in or may be inferred from a broadcast UAV contact inquiryreceived by the UAV, to a time recorded by the UAV as a result of itsown contact detection). However, claimed subject matter is not limitedto any particular described embodiments, implementations, examples, etc.

FIG. 8E illustrates a flow diagram 800E having example operations 840,842, 844, or 846. For certain example embodiments, an operation 840 maybe directed at least partially to wherein the detecting at least onemotivation to activate at least one automated hazard handling routine ofthe UFV (of operation 802) includes detecting at least a partial loss offunctionality for at least one component that is capable of supportinghazard detection. For certain example implementations, at least onemachine may detect (e.g., via at least one detection 712) at least apartial (e.g., loss of one of multiple features or capabilities,reduction in efficacy beyond a threshold, complete destruction,inability to diagnose health of a component, or a combination thereof,etc.) loss of functionality 744 (e.g., inability to attain a desiredsensor reading, inability to achieve a goal, inability to accept orrespond to command inputs, imprecise readings, lack of ability tofulfill intended purpose or expected capability, or a combinationthereof, etc.) for at least one component 746 (e.g., any one or more ofcomponents described hereinabove with particular reference to FIG. 4 or6A, such as a part of a power train 416 a, a part of a steering assembly416 b, a visual sensor, a wind speed sensor, a navigational sensor, acontrol module, or a combination thereof, etc.) that is capable ofsupporting hazard detection (e.g., that may facilitate or enable theaddressing, reacting to, or a combination thereof, etc. or otherotherwise handling at least one remote UFV 102R, at least one firstremote UFV 102R(1), at least one second remote UFV 102R(2), at least onePOFV 302, at least one other object that may present a collision risk,at least one weather-related condition, at least one obstacle to amission objective, at least one hindrance to accomplishing a task, atleast one delay to achieving a goal, or a combination thereof, etc.). Byway of example but not limitation, at least one UFV may detect at leasta partial loss of functionality for at least one component that iscapable of supporting hazard detection. (e.g., a UAV may run adiagnostic that determines a high likelihood that a particular componentof the UAV is not functioning within safe or accurate or recommendedoperating parameters or may realize that control circuitry is no longerreceiving output or responses from a particular component). However,claimed subject matter is not limited to any particular describedembodiments, implementations, examples, etc.

For certain example embodiments, an operation 842 may be directed atleast partially to wherein the detecting at least a partial loss offunctionality for at least one component that is capable of supportinghazard detection (of operation 840) includes detecting the at least apartial loss of functionality for at least one visual spectrum sensor ofthe UFV. For certain example implementations, at least one machine maydetect at least a partial loss of functionality 744 for at least onevisual spectrum sensor 748 (e.g., a device that converts an opticalimage into an electronic signal, an imaging sensor, a charge-coupleddevice (CCD) sensor, a camera, a complementary metal-oxide-semiconductor(CMOS) sensor, a pixel sensor, an analog sensor, a digital sensor, asensor that is capable of detecting electromagnetic waves in ahuman-perceptible visual spectrum, or a combination thereof, etc.) of aUFV 102. By way of example but not limitation, at least one UFV maydetect the at least a partial loss of functionality for at least onevisual spectrum sensor of the UFV. (e.g., a UAV may detect that adirectional or focusing capability of at least one camera has ceased tofunction, with the at least one camera ordinarily usable by a remotehuman pilot to identify hazards to the UAV). However, claimed subjectmatter is not limited to any particular described embodiments,implementations, examples, etc.

For certain example embodiments, an operation 844 may be directed atleast partially to wherein the detecting at least a partial loss offunctionality for at least one component that is capable of supportinghazard detection (of operation 840) includes detecting the at least apartial loss of functionality for at least one satellite positioningsystem (SPS) unit of the UFV. For certain example implementations, atleast one machine may detect at least a partial loss of functionality744 for at least one satellite positioning system (SPS) unit 750 (e.g.,a device that is capable of converting one or more signals from one ormore satellites into one or more positional coordinates; a device thatis capable of generating GPS, GLONASS, or Galileo coordinates; a devicethat can provide at least part of an SPS positional fix; or acombination thereof; etc.) of a UFV 102. By way of example but notlimitation, at least one UFV may detect the at least a partial loss offunctionality for at least one SPS unit of the UFV. (e.g., a UAV maydetect that a GPS chip is no longer providing a GPS fix to a navigationmodule). However, claimed subject matter is not limited to anyparticular described embodiments, implementations, examples, etc.

For certain example embodiments, an operation 846 may be directed atleast partially to wherein the detecting at least a partial loss offunctionality for at least one component that is capable of supportinghazard detection (of operation 840) includes detecting the at least apartial loss of functionality for at least one radio of the UFV. Forcertain example implementations, at least one machine may detect atleast a partial loss of functionality 744 for at least one radio 604(e.g., a device that utilizes wireless transmission of signals throughfree space by electromagnetic radiation at one or more frequencies belowthat of visible light, an aircraft radio, a radio for an R/C vehicle, aradio that utilizes VHF radio spectrum allocated to civil aviationcommunication, a short-range radio, a Wi-Fi radio, a Wi-Maxx radio, aBluetooth radio, a long-range radio, a mobile phone transceiver, an LTEchip, or a combination thereof, etc.) of a UFV 102. By way of examplebut not limitation, at least one UFV may detect the at least a partialloss of functionality for at least one radio of the UFV. (e.g., a UAVmay detect that it cannot receive a signal via a short-range radio(e.g., a Bluetooth or Wi-Fi capable transceiver, which may be used forinter-UFV communications for local inter-UFV flight coordination) evenif a longer-range radio continues to function). However, claimed subjectmatter is not limited to any particular described embodiments,implementations, examples, etc.

FIGS. 9A-9B depict example additions or alternatives for a flow diagramof FIG. 8A in accordance with certain example embodiments. Asillustrated, flow diagrams of FIGS. 9A-9B may include any of theillustrated or described operations. Although operations are shown ordescribed in a particular order or with a particular relationship to oneor more other operations, it should be understood that methods may beperformed in alternative manners without departing from claimed subjectmatter, including, but not limited to, with a different order or numberof operations or with a different relationship between or amongoperations (e.g., operations that are illustrated as nested blocks arenot necessarily subsidiary operations and may instead be performedindependently). Also, at least some operation(s) of flow diagrams ofFIGS. 9A-9B may be performed so as to be fully or partially overlappingwith other operation(s). For certain example embodiments, one or moreoperations of flow diagrams 900A-900B (of FIGS. 9A-9B) may be performedby at least one machine (e.g., a UFV 102 or at least a portion thereof).

FIG. 9A illustrates a flow diagram 900A having example operations 910,912, 914, or 916. For certain example embodiments, an operation 910 maybe directed at least partially to wherein the activating the at leastone automated hazard handling routine of the UFV based at leastpartially on the at least one motivation (of operation 804) includesconsulting at least one map to adjust at least one flight path of theUFV. For certain example implementations, at least one machine mayconsult (e.g., review, refer to, inspect, utilize data from, applyinformation garnered from, or a combination thereof, etc.) at least onemap 754 (e.g., terrain description, visual or symbolic representation ofan area, a navigational aid depicting geography—such as naturalattributes of land or man-made structures, or a combination thereof,etc.) to adjust (e.g., change, decrease speed or altitude of, increasespeed or altitude of, change direction for, replace, cause a deviationin, adapt, modify, alter, deviate from, add something to, take somethingaway from, or a combination thereof, etc.) at least one flight path 756(e.g., a heading, a flight trajectory, a position, an altitude, a speed,a direction a velocity, an acceleration, a stability level, adestination, a course through air or space or a time at which the courseis to be traversed, or a combination thereof, etc.) of a UFV 102. By wayof example but not limitation, at least one UFV may consult at least onemap to adjust at least one flight path of the UFV. (e.g., a UAV mayrefer to a topographical map to determine whether to climb in altitudeor veer left or right to avoid an upcoming hill). However, claimedsubject matter is not limited to any particular described embodiments,implementations, examples, etc.

For certain example embodiments, an operation 912 may be directed atleast partially to wherein the consulting at least one map to adjust atleast one flight path of the UFV (of operation 910) includes inspectingthe at least one map to ascertain at least one three-dimensionalrepresentation of one or more hazards to adjust the at least one flightpath of the UFV. For certain example implementations, at least onemachine may inspect (e.g., study, analyze, extract information from, ora combination thereof, etc.) at least one map 754 to ascertain (e.g.,determine, discover, acquire, or a combination thereof, etc.) at leastone three-dimensional representation 758 (e.g., a description includingmore than two dimensions, an indication of height of topography orbuildings, a set of electronic coordinates in X-Y-Z directions for atleast one object located on a map, or a combination thereof, etc.) ofone or more hazards (e.g., at least one object that may present acollision risk, at least one weather-related condition, at least oneother flying vehicle, at least one physical obstacle to a missionobjective, at least one building or tower, or a combination thereof,etc.) to adjust at least one flight path of a UFV 102. By way of examplebut not limitation, at least one UFV may inspect the at least one map toascertain at least one three-dimensional representation of one or morehazards to adjust the at least one flight path of the UFV. (e.g., a UAVmay analyze an electronic map to extract one or more indicators ofcoordinates that indicate positions in space of a set of buildings,including corners thereof, so that the UAV can plot a course safelythrough the set of buildings). However, claimed subject matter is notlimited to any particular described embodiments, implementations,examples, etc.

For certain example embodiments, an operation 914 may be directed atleast partially to wherein the activating the at least one automatedhazard handling routine of the UFV based at least partially on the atleast one motivation (of operation 804) includes beginning a controlleddescent responsive at least partly to activation of the at least oneautomated hazard handling routine of the UFV. For certain exampleimplementations, at least one machine may begin a controlled descent 760(e.g., a reduction in altitude under operation of a flight controlmodule, a descent that retards gravity's attraction, a setting orestablishment of a flight path toward the earth, or a combinationthereof, etc.) responsive at least partly to activation (e.g., via atleast one activation 714) of at least one automated hazard handlingroutine 710 of a UFV 102. By way of example but not limitation, at leastone UFV may begin a controlled descent responsive at least partly toactivation of the at least one automated hazard handling routine of theUFV. (e.g., a UAV may, upon an unexpected activation of self-guidedflight, begin to descend toward the earth aiming for asufficiently-sized flat piece of land that is not currently blocked byother objects). However, claimed subject matter is not limited to anyparticular described embodiments, implementations, examples, etc.

For certain example embodiments, an operation 916 may be directed atleast partially to wherein the activating the at least one automatedhazard handling routine of the UFV based at least partially on the atleast one motivation (of operation 804) includes broadcasting at leastone indication of a maneuverability quality corresponding to the UFVresponsive at least partly to activation of the at least one automatedhazard handling routine of the UFV. For certain example implementations,at least one machine may broadcast 762 (e.g., transmit in the open, sendwithout encryption, communicate to multiple recipients, transmit forpossible unknown potential recipients, communicate without knowing ifall relevant receivers are known a priori, or a combination thereof,etc.) at least one indication of a maneuverability quality 762 (e.g.,(1) a label or value representative of how well a UFV can adjust itsflight path; (2) a relative indication; (3) an absolute indication; (4)a score; (5) a class—like a regulatory certification class for (5a)meeting at least one predetermined maneuverability criterion, such ashovering, acceleration, minimum velocity, stability in particularweather conditions, or a combination thereof, etc., (5b) comportmentwith a set of construction or feature regulations for a craft type, (5c)a label equating to a set of minimal standards to achieve the label, or(5d) some combination thereof, etc.—; (6) a rating—like an industrycertification rating for (6a) meeting at least one predeterminedmaneuverability criterion, such as hovering, acceleration, minimumvelocity, stability in particular weather conditions, or a combinationthereof, etc., (6b) comportment with a set of flight capabilities, (6c)a grade representing a maneuvering score achieved by a make or model ofa vehicle, (6d) a title equating to a set of minimal standards, such asa minimum negative acceleration, to earn the title, or (6e) somecombination thereof, etc.—; (7) a level; (8) an indication of a degreeto which a vehicle is agile; (9) a craft category, such as fixed wing,rotary wing, LTA, ornithopter, or a combination thereof, etc.; (10) somecombination thereof; or so forth) corresponding to a UFV 102 responsiveat least partly to activation of at least one automated hazard handlingroutine 710 of UFV 102. By way of example but not limitation, at leastone UFV may broadcast at least one indication of a maneuverabilityquality corresponding to the UFV responsive at least partly toactivation of the at least one automated hazard handling routine of theUFV. (e.g., a UAV may begin transmitting to UAVs within radio signalrange a class name of a vehicle class to which the UAV belongs, such asLTA or rotating wing). However, claimed subject matter is not limited toany particular described embodiments, implementations, examples, etc.

FIG. 9B illustrates a flow diagram 900B having example operations 920,922, 924, or 926. For certain example embodiments, an operation 920 maybe directed at least partially to wherein the activating the at leastone automated hazard handling routine of the UFV based at leastpartially on the at least one motivation (of operation 804) includespreparing at least one plan for at least one flight path for the UFVbased at least partially on one or more governmental constraints. Forcertain example implementations, at least one machine may prepare (e.g.,construct, formulate, produce, generate, assemble, or a combinationthereof, etc.) at least one plan 766 (e.g., scheme, stratagem, course ofaction, intention, aim, or a combination thereof, etc.) for at least oneflight path 756 (e.g., a heading, a flight trajectory, a position, analtitude, a speed, a direction a velocity, an acceleration, a stabilitylevel, a destination, a course through air or space or a time at whichthe course is to be traversed, or a combination thereof, etc.) for a UFV102 based at least partially on one or more governmental constraints 768(e.g., rules, regulations, laws, ordnances, limitations, restrictions,requirements, guidelines, obligations, mandates, or a combinationthereof, etc.). By way of example but not limitation, at least one UFVmay prepare at least one plan for at least one flight path for the UFVbased at least partially on one or more governmental constraints. (e.g.,a UAV may determine a flight path adjustment to avoid violating one ormore FAA flight constraints for the area it is in or the type of craftthat it is). However, claimed subject matter is not limited to anyparticular described embodiments, implementations, examples, etc.

For certain example embodiments, an operation 922 may be directed atleast partially to wherein the preparing at least one plan for at leastone flight path for the UFV based at least partially on one or moregovernmental constraints (of operation 920) includes preparing the atleast one plan for the at least one flight path for the UFV based atleast partially on at least one of (i) one or more speed limits or (ii)one or more altitude restrictions. For certain example implementations,at least one machine may prepare (e.g., construct, formulate, produce,generate, assemble, or a combination thereof, etc.) at least one plan766 (e.g., scheme, stratagem, course of action, intention, aim, or acombination thereof, etc.) for at least one flight path 756 (e.g., aheading, a flight trajectory, a position, an altitude, a speed, adirection a velocity, an acceleration, a stability level, a destination,a course through air or space or a time at which the course is to betraversed, or a combination thereof, etc.) for a UFV 102 based at leastpartially on at least one of (i) one or more speed limits (e.g., maximumpermitted air speed, velocity restriction, minimum air speed,recommended speed, speed limit based at least partly on altitude, speedlimit based at least partly on location, speed limit based at leastpartly on craft type, or a combination thereof, etc.) or (ii) one ormore altitude restrictions (e.g., minimum permitted altitude, approvedaltitude range, altitude requirement based partly on speed, altitudeobligation based partly on location, altitude constraint based on crafttype, maximum permissible height above the earth, or a combinationthereof, etc.). By way of example but not limitation, at least one UFVmay prepare the at least one plan for the at least one flight path forthe UFV based at least partially on at least one of (i) one or morespeed limits or (ii) one or more altitude restrictions. (e.g., a UAV mayplan a course through upcoming terrain that stays below current airspeedlimits, which may be “posted” via electronic broadcasts, and that staysabove FAA-promulgated minimum altitude requirements). However, claimedsubject matter is not limited to any particular described embodiments,implementations, examples, etc.

For certain example embodiments, an operation 924 may be directed atleast partially to wherein the activating the at least one automatedhazard handling routine of the UFV based at least partially on the atleast one motivation (of operation 804) includes preparing at least oneplan for at least one flight path for the UFV based at least partiallyon at least one populated area. For certain example implementations, atleast one machine may prepare (e.g., construct, formulate, produce,generate, assemble, or a combination thereof, etc.) at least one plan766 (e.g., scheme, stratagem, course of action, intention, aim, or acombination thereof, etc.) for at least one flight path 756 (e.g., aheading, a flight trajectory, a position, an altitude, a speed, adirection a velocity, an acceleration, a stability level, a destination,a course through air or space or a time at which the course is to betraversed, or a combination thereof, etc.) for a UFV 102 based at leastpartially on at least one populated area 770 (e.g., an area with people,a region with relatively high population density, an area with homes, aneighborhood as opposed to an empty field, a town as opposed tocountryside, an apartment building as opposed to a parking lot, or acombination thereof, etc.). By way of example but not limitation, atleast one UFV may prepare at least one plan for at least one flight pathfor the UFV based at least partially on at least one populated area.(e.g., a UAV may formulate a flight trajectory responsive to, andsubstantially away from, a location of a subdivision that is identifiedon a map of surrounding terrain). However, claimed subject matter is notlimited to any particular described embodiments, implementations,examples, etc.

For certain example embodiments, an operation 926 may be directed atleast partially to wherein the preparing at least one plan for at leastone flight path for the UFV based at least partially on at least onepopulated area (of operation 924) includes preparing the at least oneplan for the at least one flight path for the UFV based at leastpartially on one or more areas having at least one heat signature. Forcertain example implementations, at least one machine may prepare (e.g.,construct, formulate, produce, generate, assemble, or a combinationthereof, etc.) at least one plan 766 (e.g., scheme, stratagem, course ofaction, intention, aim, or a combination thereof, etc.) for at least oneflight path 756 (e.g., a heading, a flight trajectory, a position, analtitude, a speed, a direction a velocity, an acceleration, a stabilitylevel, a destination, a course through air or space or a time at whichthe course is to be traversed, or a combination thereof, etc.) for a UFV102 based at least partially on one or more areas (e.g., region,territory, identifiable portion of geography, a city, a neighborhood, ablock, a building, a house, a car, or a combination thereof, etc.)having at least one heat signature 772 (e.g., a shape or size orintensity of increased warmth relative to surroundings, a shape or sizeconsistent with a human, a size or intensity consistent with a group ofhumans, a shape or size consistent with an automobile, a shape or sizeor intensity consistent with a human dwelling, a detectable level ofheat that matches a human activity, or a combination thereof, etc.). Byway of example but not limitation, at least one UFV may prepare the atleast one plan for the at least one flight path for the UFV based atleast partially on one or more areas having at least one heat signature.(e.g., a UAV may make a flight control decision to steer away from anarea that registers heat above a certain level or that registers heatgreater than a threshold differential from surround heat levels asdetectable via an onboard infrared sensor). However, claimed subjectmatter is not limited to any particular described embodiments,implementations, examples, etc.

FIG. 10A depicts example additions or alternatives for a flow diagram ofFIG. 8A in accordance with certain example embodiments. As illustrated,a flow diagram of FIG. 10A may include any of the illustrated ordescribed operations. Although operations are shown or described in aparticular order or with a particular relationship to one or more otheroperations, it should be understood that methods may be performed inalternative manners without departing from claimed subject matter,including, but not limited to, with a different order or number ofoperations or with a different relationship between or among operations(e.g., operations that are illustrated as nested blocks are notnecessarily subsidiary operations and may instead be performedindependently). Also, at least some operation(s) of a flow diagram ofFIG. 10A may be performed so as to be fully or partially overlappingwith other operation(s). For certain example embodiments, one or moreoperations of flow diagram 1000A (of FIG. 10A) may be performed by atleast one machine (e.g., a UFV 102 or at least a portion thereof).

FIG. 10A illustrates a flow diagram 1000A having an example operation806. For certain example embodiments, an operation 806 may be directedat least partially to wherein a method further includes implementing oneor more additional operations. For certain example implementations, atleast one machine may implement one or more operations in addition todetecting (of operation 802) or activating (of operation 804). Exampleadditional operations may include, by way of example but not limitation,1010, 1012, 1014, or 1016 (of FIG. 10A).

FIG. 10A illustrates a flow diagram 1000A having example operations1010, 1012, 1014, 1016, or 1018. For certain example embodiments, anoperation 1010 may be directed at least partially to wherein a method ofdetecting (of operation 802) or activating (of operation 804) furtherincludes (at additional operation 806) attempting to communicate with abase station that is associated with the UFV via at least one other UFV.For certain example implementations, at least one machine may attempt tocommunicate with (e.g., send a message to, receive an instruction from,exchange telemetry or control signals with, or a combination thereof,etc.) a base station 306 that is associated with (e.g., corresponds to,is related to, is linked to, is empowered to control, is capable ofadjusting a flight path of, or a combination thereof, etc.) a UFV 102via at least one other UFV (e.g., a remote UFV 102R). By way of examplebut not limitation, at least one UFV may attempt to communicate with abase station that is associated with the UFV via at least one other UFV.(e.g., a UAV that has lost contact with its base station may attempt toroute a communication through another UAV, which other UAV is closer toor otherwise capable of communicating with, the base station of the UAV,thereby using the other UAV as an intermediary or relay). However,claimed subject matter is not limited to any particular describedembodiments, implementations, examples, etc.

For certain example embodiments, an operation 1012 may be directed atleast partially to wherein a method of detecting (of operation 802) oractivating (of operation 804) further includes (at additional operation806) obeying a received communication indicative that at least oneparticular sensor of the UFV is not to be employed by the UFV. Forcertain example implementations, at least one machine may obey (e.g.,abide by, follow, adhere to, implement, or a combination thereof, etc.)a received communication 776 (e.g., a message, a signal, a packet, abeacon, or a combination thereof, etc.) indicative that at least oneparticular sensor 778 (e.g., a visual camera, an infrared camera, areceiver, a particular kind of radio, a GPS receiver, or a combinationthereof, etc.) of a UFV 102 is not to be employed (e.g., turned on, madeactive, utilized, used in a recording mode, deployed for data that is tobe retained, used outside of what is required for safe navigation, or acombination thereof, etc.) by UFV 102. By way of example but notlimitation, at least one UFV may obey a received communicationindicative that at least one particular sensor of the UFV is not to beemployed by the UFV. (e.g., a UAV may follow a communication that isreceived from a ground location, such as a particular company's privateand confidential research facility, with the received communicationincluding a standardized command instructing UAVs in the area that theyare not permitted to image the ground with a camera sensor). However,claimed subject matter is not limited to any particular describedembodiments, implementations, examples, etc.

For certain example embodiments, an operation 1014 may be directed atleast partially to wherein a method of detecting (of operation 802) oractivating (of operation 804) further includes (at additional operation806) deactivating the at least one automated hazard handling routine ofthe UFV based at least partially on at least one deactivation commandreceived from a base station that is associated with the UFV. Forcertain example implementations, at least one machine may deactivate 780(e.g., cease applying, turn off, shut down, discontinue use of, or acombination thereof, etc.) at least one automated hazard handlingroutine 710 of a UFV 102 based at least partially on at least onedeactivation command 782 (e.g., instruction, order, signal, message, ora combination thereof, etc.) received from a base station 306 that isassociated with (e.g., corresponds to, is related to, is linked to, isempowered to control, is capable of adjusting a flight path of, or acombination thereof, etc.) UFV 102. By way of example but notlimitation, at least one UFV may deactivate the at least one automatedhazard handling routine of the UFV based at least partially on at leastone deactivation command received from a base station that is associatedwith the UFV. (e.g., a UAV may deactivate an onboard collision avoidancesystem responsive at least partly to a command to deactivate thecollision avoidance system that is received from a base station that hasauthority to adjust a flight path of the UAV). However, claimed subjectmatter is not limited to any particular described embodiments,implementations, examples, etc.

For certain example embodiments, an operation 1016 may be directed atleast partially to wherein the deactivating the at least one automatedhazard handling routine of the UFV based at least partially on at leastone deactivation command received from a base station that is associatedwith the UFV (of operation 1014) includes authenticating that the atleast one deactivation command was formulated by the base station thatis associated with the UFV. For certain example implementations, atleast one machine may authenticate 784 (e.g., determine truth of,ascertain if alleged origin is accurate, ensure purported identity isactual identity, or a combination thereof, etc.) that at least onedeactivation command 782 (e.g., instruction, order, signal, message, ora combination thereof, etc.) was formulated (e.g., prepared,constructed, created, generated, or a combination thereof, etc.) by abase station 306 that is associated with (e.g., corresponds to, isrelated to, is linked to, is empowered to control, is capable ofadjusting a flight path of, or a combination thereof, etc.) a UFV 102.By way of example but not limitation, at least one UFV may authenticatethat the at least one deactivation command was formulated by the basestation that is associated with the UFV. (e.g., a UAV may analyze areceived deactivation command—such as by considering a submittedpassword or application of a cryptographic key—to ensure that it wascreated by a base station having flight control authority over the UAV).However, claimed subject matter is not limited to any particulardescribed embodiments, implementations, examples, etc.

For certain example embodiments, an operation 1018 may be directed atleast partially to wherein the deactivating the at least one automatedhazard handling routine of the UFV based at least partially on at leastone deactivation command received from a base station that is associatedwith the UFV (of operation 1014) includes verifying that the at leastone deactivation command references at least one deactivation code thatoriginated from the base station that is associated with the UFV. Forcertain example implementations, at least one machine may verify 786(e.g., prove truth of, ensure truth via consideration of evidence,validate, confirm, or a combination thereof, etc.) that at least onedeactivation command 782 (e.g., instruction, order, signal, message, ora combination thereof, etc.) references (e.g., includes, links to,provides a mechanism to access, or a combination thereof, etc.) at leastone deactivation code 788 (e.g., a value, a set of alphanumericcharacters, a cryptographic key, an encoded value, or a combinationthereof, etc.) that originated (e.g., was created at, was generated for,is assigned to, or a combination thereof, etc.) from a base station 306that is associated with (e.g., corresponds to, is related to, is linkedto, is empowered to control, is capable of adjusting a flight path of,or a combination thereof, etc.) a UFV 102. By way of example but notlimitation, at least one UFV may verify that the at least onedeactivation command references at least one deactivation code thatoriginated from the base station that is associated with the UFV. (e.g.,a UAV may analyze a received deactivation command—such as by consideringa submitted password or application of a cryptographic key—to validatethat the command includes a deactivation code that was generated at orassigned to a base station having flight control authority over theUAV). However, claimed subject matter is not limited to any particulardescribed embodiments, implementations, examples, etc.

Those skilled in the art will appreciate that the foregoing specificexemplary processes and/or machines and/or technologies arerepresentative of more general processes and/or machines and/ortechnologies taught elsewhere herein, such as in the claims filedherewith and/or elsewhere in the present application.

Those having skill in the art will recognize that the state of the arthas progressed to the point where there is little distinction leftbetween hardware, software, and/or firmware implementations of aspectsof systems; the use of hardware, software, and/or firmware is generally(but not always, in that in certain contexts the choice between hardwareand software can become significant) a design choice representing costvs. efficiency tradeoffs. Those having skill in the art will appreciatethat there are various vehicles by which processes and/or systems and/orother technologies described herein can be effected (e.g., hardware,software, and/or firmware), and that the preferred vehicle will varywith the context in which the processes and/or systems and/or othertechnologies are deployed. For example, if an implementer determinesthat speed and accuracy are paramount, the implementer may opt for amainly hardware and/or firmware vehicle; alternatively, if flexibilityis paramount, the implementer may opt for a mainly softwareimplementation; or, yet again alternatively, the implementer may opt forsome combination of hardware, software, and/or firmware. Hence, thereare several possible vehicles by which the processes and/or devicesand/or other technologies described herein may be effected, none ofwhich is inherently superior to the other in that any vehicle to beutilized is a choice dependent upon the context in which the vehiclewill be deployed and the specific concerns (e.g., speed, flexibility, orpredictability) of the implementer, any of which may vary. Those skilledin the art will recognize that optical aspects of implementations willtypically employ optically-oriented hardware, software, and or firmware.

In some implementations described herein, logic and similarimplementations may include software or other control structures.Electronic circuitry, for example, may have one or more paths ofelectrical current constructed and arranged to implement variousfunctions as described herein. In some implementations, one or moremedia may be configured to bear a device-detectable implementation whensuch media hold or transmit device detectable instructions operable toperform as described herein. In some variants, for example,implementations may include an update or modification of existingsoftware or firmware, or of gate arrays or programmable hardware, suchas by performing a reception of or a transmission of one or moreinstructions in relation to one or more operations described herein.Alternatively or additionally, in some variants, an implementation mayinclude special-purpose hardware, software, firmware components, and/orgeneral-purpose components executing or otherwise invokingspecial-purpose components. Specifications or other implementations maybe transmitted by one or more instances of tangible transmission mediaas described herein, optionally by packet transmission or otherwise bypassing through distributed media at various times.

Alternatively or additionally, implementations may include executing aspecial-purpose instruction sequence or invoking circuitry for enabling,triggering, coordinating, requesting, or otherwise causing one or moreoccurrences of virtually any functional operations described herein. Insome variants, operational or other logical descriptions herein may beexpressed as source code and compiled or otherwise invoked as anexecutable instruction sequence. In some contexts, for example,implementations may be provided, in whole or in part, by source code,such as C++, or other code sequences. In other implementations, sourceor other code implementation, using commercially available and/ortechniques in the art, may be compiled/implemented/translated/convertedinto a high-level descriptor language (e.g., initially implementingdescribed technologies in C or C++ programming language and thereafterconverting the programming language implementation into alogic-synthesizable language implementation, a hardware descriptionlanguage implementation, a hardware design simulation implementation,and/or other such similar mode(s) of expression). For example, some orall of a logical expression (e.g., computer programming languageimplementation) may be manifested as a Verilog-type hardware description(e.g., via Hardware Description Language (HDL) and/or Very High SpeedIntegrated Circuit Hardware Descriptor Language (VHDL)) or othercircuitry model which may then be used to create a physicalimplementation having hardware (e.g., an Application Specific IntegratedCircuit). Those skilled in the art will recognize how to obtain,configure, and optimize suitable transmission or computational elements,material supplies, actuators, or other structures in light of theseteachings.

The foregoing detailed description has set forth various embodiments ofthe devices and/or processes via the use of block diagrams, flowcharts,and/or examples. Insofar as such block diagrams, flowcharts, and/orexamples contain one or more functions and/or operations, it will beunderstood by those within the art that each function and/or operationwithin such block diagrams, flowcharts, or examples can be implemented,individually and/or collectively, by a wide range of hardware, software,firmware, or virtually any combination thereof. In one embodiment,several portions of the subject matter described herein may beimplemented via Application Specific Integrated Circuits (ASICs), FieldProgrammable Gate Arrays (FPGAs), digital signal processors (DSPs), orother integrated formats. However, those skilled in the art willrecognize that some aspects of the embodiments disclosed herein, inwhole or in part, can be equivalently implemented in integratedcircuits, as one or more computer programs running on one or morecomputers (e.g., as one or more programs running on one or more computersystems), as one or more programs running on one or more processors(e.g., as one or more programs running on one or more microprocessors),as firmware, or as virtually any combination thereof, and that designingthe circuitry and/or writing the code for the software and or firmwarewould be well within the skill of one of skill in the art in light ofthis disclosure. In addition, those skilled in the art will appreciatethat the mechanisms of the subject matter described herein are capableof being distributed as a program product in a variety of forms, andthat an illustrative embodiment of the subject matter described hereinapplies regardless of the particular type of signal bearing medium usedto actually carry out the distribution. Examples of a signal bearingmedium include, but are not limited to, the following: a recordable typemedium such as a floppy disk, a hard disk drive, a Compact Disc (CD), aDigital Video Disk (DVD), a digital tape, a computer memory, etc.; and atransmission type medium such as a digital and/or an analogcommunication medium (e.g., a fiber optic cable, a waveguide, a wiredcommunications link, a wireless communication link (e.g., transmitter,receiver, transmission logic, reception logic, etc.), etc.).

In a general sense, those skilled in the art will recognize that thevarious aspects described herein which can be implemented, individuallyand/or collectively, by a wide range of hardware, software, firmware,and/or any combination thereof can be viewed as being composed ofvarious types of “electrical circuitry.” Consequently, as used herein“electrical circuitry” includes, but is not limited to, electricalcircuitry having at least one discrete electrical circuit, electricalcircuitry having at least one integrated circuit, electrical circuitryhaving at least one application specific integrated circuit, electricalcircuitry forming a general purpose computing device configured by acomputer program (e.g., a general purpose computer configured by acomputer program which at least partially carries out processes and/ordevices described herein, or a microprocessor configured by a computerprogram which at least partially carries out processes and/or devicesdescribed herein), electrical circuitry forming a memory device (e.g.,forms of memory (e.g., random access, flash, read only, etc.)), and/orelectrical circuitry forming a communications device (e.g., a modem,communications switch, optical-electrical equipment, etc.). Those havingskill in the art will recognize that the subject matter described hereinmay be implemented in an analog or digital fashion or some combinationthereof.

Modules, logic, circuitry, hardware and software combinations, firmware,or so forth may be realized or implemented as one or moregeneral-purpose processors, one or more processing cores, one or morespecial-purpose processors, one or more microprocessors, at least oneApplication-Specific Integrated Circuit (ASIC), at least one FieldProgrammable Gate Array (FPGA), at least one digital signal processor(DSP), some combination thereof, or so forth that is executing or isconfigured to execute instructions, a special-purpose program, anapplication, software, code, some combination thereof, or so forth as atleast one special-purpose computing apparatus or specific computingcomponent. One or more modules, logic, or circuitry, etc. may, by way ofexample but not limitation, be implemented using one processor ormultiple processors that are configured to execute instructions (e.g.,sequentially, in parallel, at least partially overlapping in atime-multiplexed fashion, at least partially overlapping across multiplecores, or a combination thereof, etc.) to perform a method or realize aparticular computing machine. For example, a first module may beembodied by a given processor executing a first set of instructions ator during a first time, and a second module may be embodied by the samegiven processor executing a second set of instructions at or during asecond time. Moreover, the first and second times may be at leastpartially interleaved or overlapping, such as in a multi-threading,pipelined, or predictive processing environment. As an alternativeexample, a first module may be embodied by a first processor executing afirst set of instructions, and a second module may be embodied by asecond processor executing a second set of instructions. As anotheralternative example, a particular module may be embodied partially by afirst processor executing at least a portion of a particular set ofinstructions and embodied partially by a second processor executing atleast a portion of the particular set of instructions. Othercombinations of instructions, a program, an application, software, orcode, etc. in conjunction with at least one processor or other executionmachinery may be utilized to realize one or more modules, logic, orcircuitry, etc. to implement any of the processing algorithms describedherein.

Those skilled in the art will recognize that at least a portion of thedevices and/or processes described herein can be integrated into a dataprocessing system. Those having skill in the art will recognize that adata processing system generally includes one or more of a system unithousing, a video display device, memory such as volatile or non-volatilememory, processors such as microprocessors or digital signal processors,computational entities such as operating systems, drivers, graphicaluser interfaces, and applications programs, one or more interactiondevices (e.g., a touch pad, a touch screen, an antenna, etc.), and/orcontrol systems including feedback loops and control motors (e.g.,feedback for sensing position and/or velocity; control motors for movingand/or adjusting components and/or quantities). A data processing systemmay be implemented utilizing suitable commercially available components,such as those typically found in data computing/communication and/ornetwork computing/communication systems.

For the purposes of this application, “cloud” computing may beunderstood as described in the cloud computing literature. For example,cloud computing may be methods and/or systems for the delivery ofcomputational capacity and/or storage capacity as a service. The “cloud”may refer to one or more hardware and/or software components thatdeliver or assist in the delivery of computational and/or storagecapacity, including, but not limited to, one or more of a client, anapplication, a platform, an infrastructure, and/or a server The cloudmay refer to any of the hardware and/or software associated with aclient, an application, a platform, an infrastructure, and/or a server.For example, cloud and cloud computing may refer to one or more of acomputer, a processor, a storage medium, a router, a switch, a modem, avirtual machine (e.g., a virtual server), a data center, an operatingsystem, a middleware, a firmware, a hardware back-end, a softwareback-end, and/or a software application. A cloud may refer to a privatecloud, a public cloud, a hybrid cloud, and/or a community cloud. A cloudmay be a shared pool of configurable computing resources, which may bepublic, private, semi-private, distributable, scaleable, flexible,temporary, virtual, and/or physical. A cloud or cloud service may bedelivered over one or more types of network, e.g., a mobilecommunication network, and the Internet.

As used in this application, a cloud or a cloud service may include oneor more of infrastructure-as-a-service (“IaaS”), platform-as-a-service(“PaaS”), software-as-a-service (“SaaS”), and/or desktop-as-a-service(“DaaS”). As a non-exclusive example, IaaS may include, e.g., one ormore virtual server instantiations that may start, stop, access, and/orconfigure virtual servers and/or storage centers (e.g., providing one ormore processors, storage space, and/or network resources on-demand,e.g., EMC and Rackspace). PaaS may include, e.g., one or more softwareand/or development tools hosted on an infrastructure (e.g., a computingplatform and/or a solution stack from which the client can createsoftware interfaces and applications, e.g., Microsoft Azure). SaaS mayinclude, e.g., software hosted by a service provider and accessible overa network (e.g., the software for the application and/or the dataassociated with that software application may be kept on the network,e.g., Google Apps, SalesForce). DaaS may include, e.g., providingdesktop, applications, data, and/or services for the user over a network(e.g., providing a multi-application framework, the applications in theframework, the data associated with the applications, and/or servicesrelated to the applications and/or the data over the network, e.g.,Citrix). The foregoing is intended to be exemplary of the types ofsystems and/or methods referred to in this application as “cloud” or“cloud computing” and should not be considered complete or exhaustive.

Those skilled in the art will recognize that it is common within the artto implement devices and/or processes and/or systems, and thereafter useengineering and/or other practices to integrate such implemented devicesand/or processes and/or systems into more comprehensive devices and/orprocesses and/or systems. That is, at least a portion of the devicesand/or processes and/or systems described herein can be integrated intoother devices and/or processes and/or systems via a reasonable amount ofexperimentation. Those having skill in the art will recognize thatexamples of such other devices and/or processes and/or systems mightinclude—as appropriate to context and application—all or part of devicesand/or processes and/or systems of (a) an air conveyance (e.g., anairplane, rocket, helicopter, etc.), (b) a ground conveyance (e.g., acar, truck, locomotive, tank, armored personnel carrier, etc.), (c) abuilding (e.g., a home, warehouse, office, etc.), (d) an appliance(e.g., a refrigerator, a washing machine, a dryer, etc.), (e) acommunications system (e.g., a networked system, a telephone system, aVoice over IP system, etc.), (f) a business entity (e.g., an InternetService Provider (ISP) entity such as Comcast Cable, Qwest, SouthwesternBell, etc.), or (g) a wired/wireless services entity (e.g., Sprint,Cingular, Nextel, etc.), etc.

In certain cases, use of a system or method may occur in a territoryeven if components are located outside the territory. For example, in adistributed computing context, use of a distributed computing system mayoccur in a territory even though parts of the system may be locatedoutside of the territory (e.g., relay, server, processor, signal-bearingmedium, transmitting computer, receiving computer, etc. located outsidethe territory). A sale of a system or method may likewise occur in aterritory even if components of the system or method are located and/orused outside the territory. Further, implementation of at least part ofa system for performing a method in one territory does not preclude useof the system in another territory.

One skilled in the art will recognize that the herein describedcomponents (e.g., operations), devices, objects, and the discussionaccompanying them are used as examples for the sake of conceptualclarity and that various configuration modifications are contemplated.Consequently, as used herein, the specific exemplars set forth and theaccompanying discussion are intended to be representative of their moregeneral classes. In general, use of any specific exemplar is intended tobe representative of its class, and the non-inclusion of specificcomponents (e.g., operations), devices, and objects should not be takenlimiting.

With respect to the use of substantially any plural and/or singularterms herein, those having skill in the art can translate from theplural to the singular and/or from the singular to the plural as isappropriate to the context and/or application. The varioussingular/plural permutations are not expressly set forth herein for sakeof clarity.

The herein described subject matter sometimes illustrates differentcomponents contained within, or connected with, different othercomponents. It is to be understood that such depicted architectures aremerely exemplary, and that in fact many other architectures may beimplemented which achieve the same functionality. In a conceptual sense,any arrangement of components to achieve the same functionality iseffectively “associated” such that the desired functionality isachieved. Hence, any two components herein combined to achieve aparticular functionality can be seen as “associated with” each othersuch that the desired functionality is achieved, irrespective ofarchitectures or intermedial components. Likewise, any two components soassociated can also be viewed as being “operably connected”, or“operably coupled,” to each other to achieve the desired functionality,and any two components capable of being so associated can also be viewedas being “operably couplable,” to each other to achieve the desiredfunctionality. Specific examples of operably couplable include but arenot limited to physically mateable and/or physically interactingcomponents, and/or wirelessly interactable, and/or wirelesslyinteracting components, and/or logically interacting, and/or logicallyinteractable components.

In some instances, one or more components may be referred to herein as“configured to,” “configured by,” “configurable to,” “operable/operativeto,” “adapted/adaptable,” “able to,” “conformable/conformed to,” etc.Those skilled in the art will recognize that such terms (e.g.“configured to”) can generally encompass active-state components and/orinactive-state components and/or standby-state components, unlesscontext requires otherwise.

This application may make reference to one or more trademarks, e.g., aword, letter, symbol, or device adopted by one manufacturer or merchantand used to identify and distinguish his or her product from those ofothers. Trademark names used herein are set forth in such language thatmakes clear their identity, that distinguishes them from commondescriptive nouns, that have fixed and definite meanings, and, in manyif not all cases, are accompanied by other specific identification usingterms not covered by trademark. In addition, trademark names used hereinhave meanings that are well-known and defined in the literature, and donot refer to products or compounds protected by trade secrets in orderto divine their meaning. All trademarks referenced in this applicationare the property of their respective owners, and the appearance of oneor more trademarks in this application does not diminish or otherwiseadversely affect the validity of the one or more trademarks. Alltrademarks, registered or unregistered, that appear in this applicationare assumed to include a proper trademark symbol, e.g., the circle R or[trade], even when such trademark symbol does not explicitly appear nextto the trademark. To the extent a trademark is used in a descriptivemanner to refer to a product or process, that trademark should beinterpreted to represent the corresponding product or process as of thedate of the filing of this patent application.

While particular aspects of the present subject matter described hereinhave been shown and described, it will be apparent to those skilled inthe art that, based upon the teachings herein, changes and modificationsmay be made without departing from the subject matter described hereinand its broader aspects and, therefore, the appended claims are toencompass within their scope all such changes and modifications as arewithin the true spirit and scope of the subject matter described herein.It will be understood by those within the art that, in general, termsused herein, and especially in the appended claims (e.g., bodies of theappended claims) are generally intended as “open” terms (e.g., the term“including” should be interpreted as “including but not limited to,” theterm “having” should be interpreted as “having at least,” the term“includes” should be interpreted as “includes but is not limited to,”etc.). It will be further understood by those within the art that if aspecific number of an introduced claim recitation is intended, such anintent will be explicitly recited in the claim, and in the absence ofsuch recitation no such intent is present. For example, as an aid tounderstanding, the following appended claims may contain usage of theintroductory phrases “at least one” and “one or more” to introduce claimrecitations. However, the use of such phrases should not be construed toimply that the introduction of a claim recitation by the indefinitearticles “a” or “an” limits any particular claim containing suchintroduced claim recitation to claims containing only one suchrecitation, even when the same claim includes the introductory phrases“one or more” or “at least one” and indefinite articles such as “a” or“an” (e.g., “a” and/or “an” should typically be interpreted to mean “atleast one” or “one or more”); the same holds true for the use ofdefinite articles used to introduce claim recitations. In addition, evenif a specific number of an introduced claim recitation is explicitlyrecited, those skilled in the art will recognize that such recitationshould typically be interpreted to mean at least the recited number(e.g., the bare recitation of “two recitations,” without othermodifiers, typically means at least two recitations, or two or morerecitations). Furthermore, in those instances where a conventionanalogous to “at least one of A, B, and C, etc.” is used, in generalsuch a construction is intended in the sense one having skill in the artwould understand the convention (e.g., “a system having at least one ofA, B, and C” would include but not be limited to systems that have Aalone, B alone, C alone, A and B together, A and C together, B and Ctogether, and/or A, B, and C together, etc.). In those instances where aconvention analogous to “at least one of A, B, or C, etc.” is used, ingeneral such a construction is intended in the sense one having skill inthe art would understand the convention (e.g., “a system having at leastone of A, B, or C” would include but not be limited to systems that haveA alone, B alone, C alone, A and B together, A and C together, B and Ctogether, and/or A, B, and C together, etc.). It will be furtherunderstood by those within the art that typically a disjunctive wordand/or phrase presenting two or more alternative terms, whether in thedescription, claims, or drawings, should be understood to contemplatethe possibilities of including one of the terms, either of the terms, orboth terms unless context dictates otherwise. For example, the phrase “Aor B” will be typically understood to include the possibilities of “A”or “B” or “A and B.”

With respect to the appended claims, those skilled in the art willappreciate that recited operations therein may generally be performed inany order. Also, although various operational flows are presented in asequence(s), it should be understood that the various operations may beperformed in other orders than those which are illustrated, or may beperformed concurrently. Examples of such alternate orderings may includeoverlapping, interleaved, interrupted, reordered, incremental,preparatory, supplemental, simultaneous, reverse, or other variantorderings, unless context dictates otherwise. Furthermore, terms like“responsive to,” “related to,” or other past-tense adjectives aregenerally not intended to exclude such variants, unless context dictatesotherwise.

While various aspects and embodiments have been disclosed herein, otheraspects and embodiments will be apparent to those skilled in the art.The various aspects and embodiments disclosed herein are for purposes ofillustration and are not intended to be limiting, with the true scopeand spirit being indicated by the following claims.

What is claimed is:
 1. A method for hazard handling for an unoccupiedflying vehicle (UFV), the method being at least partially implemented byat least one machine, the method comprising: detecting at least onemotivation to activate at least one automated hazard handling routine ofthe UFV; and activating the at least one automated hazard handlingroutine of the UFV based at least partially on the at least onemotivation.
 2. The method of claim 1, wherein the detecting at least onemotivation to activate at least one automated hazard handling routine ofthe UFV comprises: detecting at least one other UFV within a proximityzone of the UFV.
 3. The method of claim 2, wherein the detecting atleast one other UFV within a proximity zone of the UFV comprises:comparing a position of the UFV with a position of the at least oneother UFV.
 4. The method of claim 3, wherein the comparing a position ofthe UFV with a position of the at least one other UFV comprises:comparing one or more satellite positioning system (SPS) coordinatescorresponding to the position of the UFV with one or more SPScoordinates corresponding to the position of the at least one other UFV.5. The method of claim 2, wherein the detecting at least one other UFVwithin a proximity zone of the UFV comprises: receiving at the UFV atleast one proximity alert with respect to the at least one other UFV. 6.The method of claim 5, wherein the receiving at the UFV at least oneproximity alert with respect to the at least one other UFV comprises:receiving at the UFV the at least one proximity alert from the at leastone other UFV.
 7. The method of claim 5, wherein the receiving at theUFV at least one proximity alert with respect to the at least one otherUFV comprises: receiving at the UFV the at least one proximity alertfrom a base station that is associated with the UFV.
 8. The method ofclaim 5, wherein the receiving at the UFV at least one proximity alertwith respect to the at least one other UFV comprises: receiving at theUFV the at least one proximity alert from an air traffic coordinationunit.
 9. The method of claim 1, wherein the detecting at least onemotivation to activate at least one automated hazard handling routine ofthe UFV comprises: detecting physical contact with at least one object.10. The method of claim 9, wherein the detecting physical contact withat least one object comprises: detecting the physical contact with theat least one object using at least one accelerometer.
 11. The method ofclaim 9, wherein the detecting physical contact with at least one objectcomprises: detecting the physical contact with the at least one objectusing at least one contact sensor.
 12. The method of claim 9, whereinthe detecting physical contact with at least one object comprises:detecting the physical contact with at least one other UFV.
 13. Themethod of claim 12, wherein the detecting the physical contact with atleast one other UFV comprises: identifying the at least one other UFVvia at least one comparison including at least one time corresponding toat least one contact detection by the at least one other UFV.
 14. Themethod of claim 1, wherein the detecting at least one motivation toactivate at least one automated hazard handling routine of the UFVcomprises: detecting at least a partial loss of functionality for atleast one component that is capable of supporting hazard detection. 15.The method of claim 14, wherein the detecting at least a partial loss offunctionality for at least one component that is capable of supportinghazard detection comprises: detecting the at least a partial loss offunctionality for at least one visual spectrum sensor of the UFV. 16.The method of claim 14, wherein the detecting at least a partial loss offunctionality for at least one component that is capable of supportinghazard detection comprises: detecting the at least a partial loss offunctionality for at least one satellite positioning system (SPS) unitof the UFV.
 17. The method of claim 14, wherein the detecting at least apartial loss of functionality for at least one component that is capableof supporting hazard detection comprises: detecting the at least apartial loss of functionality for at least one radio of the UFV.
 18. Themethod of claim 1, wherein the activating the at least one automatedhazard handling routine of the UFV based at least partially on the atleast one motivation comprises: consulting at least one map to adjust atleast one flight path of the UFV.
 19. The method of claim 18, whereinthe consulting at least one map to adjust at least one flight path ofthe UFV comprises: inspecting the at least one map to ascertain at leastone three-dimensional representation of one or more hazards to adjustthe at least one flight path of the UFV.
 20. The method of claim 1,wherein the activating the at least one automated hazard handlingroutine of the UFV based at least partially on the at least onemotivation comprises: beginning a controlled descent responsive at leastpartly to activation of the at least one automated hazard handlingroutine of the UFV.
 21. The method of claim 1, wherein the activatingthe at least one automated hazard handling routine of the UFV based atleast partially on the at least one motivation comprises: broadcastingat least one indication of a maneuverability quality corresponding tothe UFV responsive at least partly to activation of the at least oneautomated hazard handling routine of the UFV.
 22. The method of claim 1,wherein the activating the at least one automated hazard handlingroutine of the UFV based at least partially on the at least onemotivation comprises: preparing at least one plan for at least oneflight path for the UFV based at least partially on one or moregovernmental constraints.
 23. The method of claim 22, wherein thepreparing at least one plan for at least one flight path for the UFVbased at least partially on one or more governmental constraintscomprises: preparing the at least one plan for the at least one flightpath for the UFV based at least partially on at least one of (i) one ormore speed limits or (ii) one or more altitude restrictions.
 24. Themethod of claim 1, wherein the activating the at least one automatedhazard handling routine of the UFV based at least partially on the atleast one motivation comprises: preparing at least one plan for at leastone flight path for the UFV based at least partially on at least onepopulated area.
 25. The method of claim 24, wherein the preparing atleast one plan for at least one flight path for the UFV based at leastpartially on at least one populated area comprises: preparing the atleast one plan for the at least one flight path for the UFV based atleast partially on one or more areas having at least one heat signature.26. The method of claim 1, further comprising: attempting to communicatewith a base station that is associated with the UFV via at least oneother UFV.
 27. The method of claim 1, further comprising: obeying areceived communication indicative that at least one particular sensor ofthe UFV is not to be employed by the UFV.
 28. The method of claim 1,further comprising: deactivating the at least one automated hazardhandling routine of the UFV based at least partially on at least onedeactivation command received from a base station that is associatedwith the UFV.
 29. The method of claim 28, wherein the deactivating theat least one automated hazard handling routine of the UFV based at leastpartially on at least one deactivation command received from a basestation that is associated with the UFV comprises: authenticating thatthe at least one deactivation command was formulated by the base stationthat is associated with the UFV.
 30. The method of claim 28, wherein thedeactivating the at least one automated hazard handling routine of theUFV based at least partially on at least one deactivation commandreceived from a base station that is associated with the UFV comprises:verifying that the at least one deactivation command references at leastone deactivation code that originated from the base station that isassociated with the UFV.
 31. An unoccupied flying vehicle (UFV) forhazard handling, the UFV comprising: circuitry for detecting at leastone motivation to activate at least one automated hazard handlingroutine of the UFV; and circuitry for activating the at least oneautomated hazard handling routine of the UFV based at least partially onthe at least one motivation. 32.-60. (canceled)
 61. A system for hazardhandling for an unoccupied flying vehicle (UFV), the system comprising:means for detecting at least one motivation to activate at least oneautomated hazard handling routine of the UFV; and means for activatingthe at least one automated hazard handling routine of the UFV based atleast partially on the at least one motivation. 62.-90. (canceled)